ext3 overhead - switch to another fs?

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

.

Relevant Pages

  • FC3+mdadm+UUID problem
    ... I cant get mdadm to assemble a raidarray using the --uuid option. ... Couldn't find valid filesystem superblock. ... Assemble the array with specific devices: ... Reserved blocks gid: 0 ...
    (Fedora)
  • Re: ext3 overhead - switch to another fs?
    ... This array is *only* used for sharing data over samba to my ... Filesystem magic number: 0xEF53 ... Reserved blocks uid: 0 (user root) ... Reserved blocks gid: 0 ...
    (comp.os.linux.setup)
  • Re: Electricity Cutoffs, EXT3 and Filesystems
    ... Filesystem magic number: 0xEF53 ... Default mount options: ... Reserved blocks uid: 0 (user root) ... Reserved blocks gid: 0 ...
    (Debian-User)
  • Re: Ext3 sequential read performance drop 2.6.29 -> 2.6.30,2.6.31,...
    ... the raw datas of disks and raid device: ... OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME ... Filesystem magic number: 0xEF53 ... Reserved blocks gid: 0 ...
    (Linux-Kernel)
  • Re: limits on raid
    ... I'm trying to build a 45x750G array and want to experiment with the ... I think the unwritten bit is easier than you think, you only need it on parity blocks for RAID5, not on data blocks. ... don't know if it has) is that since the filesystem an raid are integrated into one layer they can optimize the case where files are being written onto unallocated space and instead of reading blocks from disk to calculate the parity they could just put zeros in the unallocated space, potentially speeding up the system by reducing the amount of disk I/O. ...
    (Linux-Kernel)