Tag Info

New answers tagged

1

If i assume you want to do that in windows file explorer, just point it in the proper forlder and type * in the search box (it will do it recursively) Now show detail view in explorer and click on "date modified" column . And voila! you 'll have all your files recursively sorted by modification time. If you wanted that list (only filename) on a text ...


0

In Powershell, try get-childitem -recurse | sort -property creationtime


2

Add a blackout period with hourBegin = 0, hourEnd = 23.99, weekDays = 0, 2, 4, 5, 6.


1

What is going on is that ext4 is ext3 is ext2. That is to say, they are the same filesystem, just with newer features enabled. Which features are enabled are described in the superblock. Since the ext4 driver supports all previous features, it can be used to mount all older filesystems with less features enabled. The kernel kept the original code for the ...


5

If you are just following orders, please ask the person issuing them how much usable space each filesystem needs for present and future requirements. You want to make sure that you're not creating nearly-full filesystems from the start! This approach to filesystem allocation is not scalable, so I strongly suggest that it be redesigned with a more modern ...


1

There seems to be a catch with df and btrfs on Linux. When you ask df to locate the mount point for a mounted btrfs volume, it will do the right thing. In this case, joe is a sub-directory of /m/whale/backup. # df /srv/backup/joe Filesystem 1K-blocks Used Available Use% Mounted on /dev/md126 2930135488 307676684 2619663252 11% ...


0

There are two ways in which your excel file can be locked - it can be 'in use', as in another process has an open handle to the file, but also Microsoft Office uses special 'lock files' (called 'owner files' by Microsoft). The owner file is located in the same folder as the workbook that you tried to open. The owner file name uses the following ...


0

Thanks to caskey for pointing me in the right direction. In case someone else needs the same functionality, here is the function that converts a path to a device: #include <libudev.h> #include <stdio.h> #include <stdlib.h> #include <locale.h> #include <unistd.h> #include <string.h> #include <sys/stat.h> #include ...


0

fstat() on the file returns a struct stat which contains a field of type dev_t. There are macros which will extract the major and minor device numbers. Those uniquely identify a drive and partition on a system.


0

The only reliable way to determine the real physical block size is by querying the disk directly with hdparm: hdparm -I /dev/sdX | grep Physical All linux tools like parted, tune2fs, fdisk, also the kernel (via the value provided in /proc) output 512 Bytes for disks I have which are denoted 4K by hdparm. (5 HDDs tested, with two being 4K ones.)


0

I've figured out how to do this. The key is kpartx to make the LVM usable by parted outside the VM (so on the Hypervisor host). Then you modify the partition size, then you boot the guest and increase the filesystem. So if you have a guest named TESTVM that has its storage at /dev/VMS/VIRT-TESTVM, you'd do the following on the hypervisor host: # kpartx -a ...


1

I see that dummzeuch find a solution to his problem but there is actually one more case I found where disk can have enough inodes/free space and still showing "no space left on the device" while attempting to transfer certain directories. This is caused by hash collisions on block devices formatted with ext4 file system where directory indexing is enabled ...


1

stat is not the right tool to investigate block devices. Here is an example of using --set-capacity: root@maxim:~# blockdev --getsize64 /dev/loop0 0 root@maxim:~# dd if=/dev/zero of=/tmp/aaa.img count=10 bs=1M 10+0 записей получено 10+0 записей отправлено скопировано 10485760 байт (10 MB), 0,00709284 c, 1,5 GB/c root@maxim:~# blockdev --getsize64 ...


0

The mtree from FreeBSD ships as /usr/bin/fmtree with the freebsd-buildutils* package in Ubuntu 14.04. http://packages.ubuntu.com/trusty/freebsd-buildutils


3

There seems to be a known bug in the dir_index feature (which you should be able to disable) that is caused by hashes of filenames colliding: http://blog.merovius.de/2013/10/20/ext4-mysterious-no-space-left-on.html


1

I am not sure if this fits your purpose, but have you considered tar to combine multiple files? That might decrease the pressure and space requirements on the filesystem, and your database application can read data for a specific file with one of the many tar libraries around. Depending on your access pattern this might even increase the performance.


7

You probably just want to use XFS. It's quite capable of what you're asking for, and does the job. There's no reason to complicate this with lesser-used filesystems, which can come with other tradeoffs. Please see: How does the number of subdirectories impact drive read / write performance on Linux? and The impact of a high directory-to-file ratio on XFS ...


2

Seeing the number of small files, I would consider using SquashFS. Especially if you have powerful enough CPU (meaning no Pentium III, or 1GHz ARM). Depending on the type of data stored, SquashFS can greatly reduce its size and thus the I/O when reading it. Only downside is CPU usage on read. On the other hand, any modern CPU can decompress at speeds far ...


2

If it is read-only, why to not use a ISO file? You can use genisoimage or mkisofs. If you want to compress the whole thing, you can also use squashfs, another read-only filesystem with very high compression ratio.



Top 50 recent answers are included