search for: minixdf

...une2fs tell me. > > By default, df on extN assumes that metadata used by the filesystem > was never available for your use and is not part of the filesystem > space. > > Documentation/filesystems/ext3.txt says: > > bsddf (*) Make 'df' act like BSD. > minixdf Make 'df' act like Minix. > > which is pretty unhelpful I suppose. ;) > > The mount man page is a little more helpful: > > bsddf|minixdf > Set the behaviour for the statfs system call. The minixdf > behaviour...

...ich is 211480576 bytes smaller than what tune2fs tell me. By default, df on extN assumes that metadata used by the filesystem was never available for your use and is not part of the filesystem space. Documentation/filesystems/ext3.txt says: bsddf (*) Make 'df' act like BSD. minixdf Make 'df' act like Minix. which is pretty unhelpful I suppose. ;) The mount man page is a little more helpful: bsddf|minixdf Set the behaviour for the statfs system call. The minixdf behaviour is to return in the f_blocks field th...

...default, df on extN assumes that metadata used by the filesystem >> was never available for your use and is not part of the filesystem >> space. >> >> Documentation/filesystems/ext3.txt says: >> >> bsddf (*) Make 'df' act like BSD. >> minixdf Make 'df' act like Minix. >> >> which is pretty unhelpful I suppose. ;) >> >> The mount man page is a little more helpful: >> >> bsddf|minixdf >> Set the behaviour for the statfs system call. The minixdf &g...

...that metadata used by the filesystem >>> was never available for your use and is not part of the filesystem >>> space. >>> >>> Documentation/filesystems/ext3.txt says: >>> >>> bsddf (*) Make 'df' act like BSD. >>> minixdf Make 'df' act like Minix. >>> >>> which is pretty unhelpful I suppose. ;) >>> >>> The mount man page is a little more helpful: >>> >>> bsddf|minixdf >>> Set the behaviour for the statfs sy...

Hello guys, I have some difficulties to understand what really are the numbers behing "df" and tune2fs. You'll find the output of tune2fs and df below, on which my maths are based. Here are my maths: A tune2fs on an ext3 FS tell me the FS size is 3284992 block large. It also tell me that the size of one block is 4096 (bytes if I'm not wrong?). So my maths tell me that the disk

...ilesystem >>>> was never available for your use and is not part of the filesystem >>>> space. >>>> >>>> Documentation/filesystems/ext3.txt says: >>>> >>>> bsddf (*) Make 'df' act like BSD. >>>> minixdf Make 'df' act like Minix. >>>> >>>> which is pretty unhelpful I suppose. ;) >>>> >>>> The mount man page is a little more helpful: >>>> >>>> bsddf|minixdf >>>> Set the b...

...963456 fsfile # mkfs.ext4 fsfile # mount -o loop fsfile # df mnt/ Filesystem 1K-blocks Used Available Use% Mounted on /tmp/fsfile 460865340 71736 437359888 1% /tmp/mnt Hm, that doesn't have the same "1k blocks" value as you saw. What if we mount it with minixdf, which doesn't "hide" fs-internal metadata from the totals? # umount mnt/ # mount -o minixdf,loop fsfile mnt # df mnt/ Filesystem 1K-blocks Used Available Use% Mounted on /tmp/fsfile 468346644 7553040 437359888 2% /tmp/mnt now the 1k-blocks total matches...

Hello everybody, first of all thank you the development of Ext2/3/4. It works like a charm and makes it possible to base applications on it. However, now I have the first time where I need more information to understand the behaviour of a ext4 installation on a 480 GB harddisk. It holds a database with a size of 355 GB, as said by "du -m": ... 355263 /opt/ssd However,

Can anyone tell me the history of CONFIG_EXT{2,3}_CHECK? There is code for a "check" option for mount if these options are enabled, but there's no way to enable them. TIA Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.