SEO

How much overhead is ext3 supposed to take? I have a RAID1 array with
two 400 GB drives, but the output of df is:

Filesystem Size Used Avail Use% Mounted on
/dev/md0 233G 214G 20G 92% /data

As you can see, there is only 233 GB! Between the manufacturer lies
and fs overhead, I expected something more like 300 GB of usable space.
Are there any tweaks I can make to get more space? I've already
removed all of the reserved root blocks (aside: is this a bad idea?
This array is *only* used for sharing data over samba to my
windows/xbmc machines). Would switching to another fs increase the
total usable size of the array?

Thanks,
Dan


tune2fs output is:

Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: c60d9346-94d4-4957-bd3e-3c869c9c2bd3
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery
sparse_super
large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 238592
Block count: 61048976
Reserved block count: 0
Free blocks: 5068254
Free inodes: 205093
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 128
Inode blocks per group: 4
Filesystem created: Sun Nov 20 22:38:36 2005
Last mount time: Sun Aug 27 22:23:35 2006
Last write time: Sun Aug 27 22:23:35 2006
Mount count: 10
Maximum mount count: 39
Last checked: Thu Jun 22 07:12:42 2006
Check interval: 15552000 (6 months)
Next check after: Tue Dec 19 06:12:42 2006
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: 9f869fa5-0bce-4504-8b56-ab2e2c5b1483
Journal backup: inode blocks

Sorry for the extra traffic; I forgot that I had 250 GB disks in the
array instead of 400.

dan.nawrocki@gmail.com wrote:
> How much overhead is ext3 supposed to take? I have a RAID1 array with
> two 400 GB drives, but the output of df is:
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/md0 233G 214G 20G 92% /data
>
> As you can see, there is only 233 GB! Between the manufacturer lies
> and fs overhead, I expected something more like 300 GB of usable space.
> Are there any tweaks I can make to get more space? I've already
> removed all of the reserved root blocks (aside: is this a bad idea?
> This array is *only* used for sharing data over samba to my
> windows/xbmc machines). Would switching to another fs increase the
> total usable size of the array?
>
> Thanks,
> Dan
>
>
> tune2fs output is:
>
> Filesystem volume name: <none>
> Last mounted on: <not available>
> Filesystem UUID: c60d9346-94d4-4957-bd3e-3c869c9c2bd3
> Filesystem magic number: 0xEF53
> Filesystem revision #: 1 (dynamic)
> Filesystem features: has_journal filetype needs_recovery
> sparse_super
> large_file
> Default mount options: (none)
> Filesystem state: clean
> Errors behavior: Continue
> Filesystem OS type: Linux
> Inode count: 238592
> Block count: 61048976
> Reserved block count: 0
> Free blocks: 5068254
> Free inodes: 205093
> First block: 0
> Block size: 4096
> Fragment size: 4096
> Blocks per group: 32768
> Fragments per group: 32768
> Inodes per group: 128
> Inode blocks per group: 4
> Filesystem created: Sun Nov 20 22:38:36 2005
> Last mount time: Sun Aug 27 22:23:35 2006
> Last write time: Sun Aug 27 22:23:35 2006
> Mount count: 10
> Maximum mount count: 39
> Last checked: Thu Jun 22 07:12:42 2006
> Check interval: 15552000 (6 months)
> Next check after: Tue Dec 19 06:12:42 2006
> Reserved blocks uid: 0 (user root)
> Reserved blocks gid: 0 (group root)
> First inode: 11
> Inode size: 128
> Journal inode: 8
> Default directory hash: tea
> Directory Hash Seed: 9f869fa5-0bce-4504-8b56-ab2e2c5b1483
> Journal backup: inode blocks

dan.nawrocki@gmail.com wrote:
> How much overhead is ext3 supposed to take? I have a RAID1 array with
> two 400 GB drives, but the output of df is:
>
> Filesystem Size Used Avail Use% Mounted on
> /dev/md0 233G 214G 20G 92% /data
>
> As you can see, there is only 233 GB! Between the manufacturer lies

There's something more fundamentally wrong going on... has nothing
to do with ext3.

dan.nawrocki@gmail.com wrote:
> Sorry for the extra traffic; I forgot that I had 250 GB disks in the
> array instead of 400.



I guess problem is solved then!! Numbers are accurate for a 250G
drive. You could go with a non-journaled fs and pick up 20-30M or so.


>
> dan.nawrocki@gmail.com wrote:
>> How much overhead is ext3 supposed to take? I have a RAID1 array with
>> two 400 GB drives, but the output of df is:
>>
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/md0 233G 214G 20G 92% /data

In comp.os.linux.setup dan.nawrocki@gmail.com:
> dan.nawrocki@gmail.com wrote:

>> How much overhead is ext3 supposed to take? I have a RAID1 array with
>> two 400 GB drives, but the output of df is:

>> Filesystem Size Used Avail Use% Mounted on
>> /dev/md0 233G 214G 20G 92% /data

[..]

> Sorry for the extra traffic; I forgot that I had 250 GB disks
> in the array instead of 400.

LOL...I had read your initial post and was really curious about
it. Big thx for coming back and clearing things up!

Good luck

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 202: kernel panic: write-only-memory (/dev/wom0)
capacity exceeded.