Hi,

i have two server with scsi disk, i have put the same files on both the server and it report a different space occupation 2.0mb and 2.2mb, a list of the folder report the same size of each files but the total size is different!!!! i have check also block size and on both is 4096

server1:
root@lakis [/home/user/www/admin/images]# du -h
2.0M .

server2:
root@ares [/home/user/www/admin/images]# du -h
2.2M .

i add also the partition info


server1:

Disk /dev/sda: 73.2 GB, 73274490880 bytes
255 heads, 63 sectors/track, 8908 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 129 1036161 83 Linux
/dev/sda2 130 1021 7164990 83 Linux
/dev/sda3 1022 1531 4096575 83 Linux
/dev/sda4 1532 8908 59255752+ f Win95 Ext'd (LBA)
/dev/sda5 1532 1786 2048256 82 Linux swap
/dev/sda6 1787 1915 1036161 83 Linux
/dev/sda7 1916 8908 56171241 83 Linux



server2:

Disk /dev/sda: 146.1 GB, 146163105792 bytes
255 heads, 63 sectors/track, 17769 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 131 1052226 83 Linux
/dev/sda2 132 1409 10265535 83 Linux
/dev/sda3 1410 2687 10265535 83 Linux
/dev/sda4 2688 17769 121146165 5 Extended
/dev/sda5 2688 3209 4192933+ 82 Linux swap
/dev/sda6 3210 3340 1052226 83 Linux
/dev/sda7 3341 17769 115900911 83 Linux



what's wrong?

Are these ext3 filesystems? If so check if the one with more space used has the DIR_INDEX option turned on (check with tune2fs -l <partition>). Using indexing on directories provides for faster access in many cases at the cost of extra space to store the index.

yes both are ext3,qhat option i need to use with

tune2fs - | /dev/sda3

thanks

It's -l (dash letter "l"), not - |. And you need to check for the filesystem options to see if the filesystem has DIR_INDEX turned on.

DIR_INDEX is turned on on both server, if i do a ls -as now the same files have different size:

Server1:

12 xxx-xxx_02.jpg

Server2:

8 xxx-xxx_02.jpg

OK, that's weird, but there's probably a reasonable explanation for it. Can you take the md5sum of both files and post it? Also please post the tune2fs -l output for both partitions.

server 1:

tune2fs 1.32 (09-Nov-2002)
Filesystem volume name: /home
Last mounted on: <not available>
Filesystem UUID: 6b0384ac-3ca8-45ca-8aaa-8cd9120298a0
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: 7028736
Block count: 14042810
Reserved block count: 702140
Free blocks: 4470124
Free inodes: 5974261
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: Thu Apr 21 16:11:57 2005
Last mount time: Mon Nov 6 19:13:04 2006
Last write time: Mon Nov 6 19:13:04 2006
Mount count: 62
Maximum mount count: -1
Last checked: Thu Apr 21 16:11:57 2005
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID: <none>
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0



server2:

tune2fs 1.35 (28-Feb-2004)
Filesystem volume name: /home
Last mounted on: <not available>
Filesystem UUID: d64349c1-3ad6-47db-9455-c6dc15817f59
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 14499840
Block count: 28975227
Reserved block count: 1448761
Free blocks: 27500659
Free inodes: 14322014
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1024
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Thu Oct 19 23:22:15 2006
Last mount time: Wed Nov 29 11:04:46 2006
Last write time: Wed Nov 29 11:04:46 2006
Mount count: 15
Maximum mount count: -1
Last checked: Thu Oct 19 23:22:15 2006
Check interval: 0 (<none>)
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: bf74d0b5-b5c8-4f0a-8c31-dc4e0b5e6f88
Journal backup: inode blocks

Doesn't look like they both have DIR_INDEX:

#1:

#2:

Only #2 had directory indexes turned on. If the md5 sums of the files match, then this is undoubtedly the cause of the size differences. I ran into this myself when migrating data from non-indexed to indexed file systems.