Bonjour,

J'aimerais savoir d'ou vient une telle différence entre le Free blocks de la commande dumpe2fs et l'espace disponible retourné par la commande df.

df : 60499224 KB ~ 60GB

dumpe2fs : 96766098 * 4096 = 396353937408 B ~ 369 GB

soit 300 GB de différence.

Cordialement,

64443.


[root@backupvm01 scripts]# df
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/rootvg-backuplv
1479677588 1344028716 60499224 96% /opt/backups

[root@backupvm01 backups]# dumpe2fs /dev/rootvg/backuplv
dumpe2fs 1.39 (29-May-2006)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: fbf1c106-1155-4fda-86bf-a3d5e8697bff
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal 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: 187908096
Block count: 375816192
Reserved block count: 18787412
Free blocks: 96766098
Free inodes: 171958551
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 934
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Fri Dec 3 15:40:04 2010
Last mount time: Tue Jul 26 11:53:26 2011
Last write time: Tue Jul 26 11:53:26 2011
Mount count: 4
Maximum mount count: 26
Last checked: Mon Jun 27 11:19:25 2011
Check interval: 15552000 (6 months)
Next check after: Sat Dec 24 10:19:25 2011
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: 06ffa3d4-db64-4a30-93f5-b125939aac6a
Journal backup: inode blocks
Journal size: 128M