Hi,
I was wondering what the overhead of a ext3 filesystem is. I formatted a 100GB disk but have only about 86GB available after formatting. I know 100GB is actually less than really 100GB, but 86GB is pretty low.
'df' also gives some weird results:
Code:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/root 3008 3008 0 100% /
/dev/discs/disc0/part1 96014540 1480588 89656620 2% /opt
I would expect that 'used + available = 1k-blocks'?
Or should I use a different version of df (there was none included in coreutils, or e2fsprogs, so where could I find another version?) as this one also can't show any info on the inode usage...
And my shared disk (through samba) also reports having 5GB already filled, but I cannot imagine that the filesystem takes up 5GB.
Should I format my HD with different inode counts and block size?
For further information 'dumpe2fs -h' gives the following, but I don't know what everything means:
Code:
dumpe2fs 1.38 (30-Jun-2005)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: d416321a-07f4-4502-8314-a1703c99388a
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 12206080
Block count: 24386670
Reserved block count: 1219333
Free blocks: 23633488
Free inodes: 12199620
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Sat May 27 00:45:26 2006
Last mount time: Sat May 27 10:35:43 2006
Last write time: Sat May 27 10:35:43 2006
Mount count: 7
Maximum mount count: 23
Last checked: Sat May 27 00:45:26 2006
Check interval: 15552000 (6 months)
Next check after: Wed Nov 22 23:45:26 2006
Reserved blocks uid: 0 (user admin)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: d3034259-0ef9-4837-91a3-8a182c830272
Journal backup: inode blocks
Is this related to the 'reserved blocks'?
Since I'm only going to use the disk for media files and not millions of small files, I could manage with less inodes, shouldn't I?
And how can I see the journal size?
thanks,
Mox