Quote:
Originally Posted by druuna
Hi,
Assuming that this disk is ext2 or ext3, what does the following command show: tune2fs -l /dev/sdc1
I'm suspecting the reserved blocks (default 5% of all space) to be the culprit.
If this is true, then the following command will reduce this to 1% (see man page tune2fs for details):
tune2fs -m 1 /dev/sdc1
Hope this helps.
|
i have given the following command in root user
[root@nixon /]# tune2fs -l /dev/sdc1
tune2fs 1.39 (29-May-2006)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: af0e4505-fdc1-4d6d-b7e9-468e41187670
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode dir_index filetype needs_reco very sparse_super large_file
Default mount options: (none)
Filesystem state: not clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 244203520
Block count: 488378000
Reserved block count: 24418900
Free blocks: 153669075
Free inodes: 239268387
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 907
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Mon Feb 22 23:46:22 2010
Last mount time: Thu May 13 17:24:55 2010
Last write time: Thu May 13 17:24:55 2010
Mount count: 59
Maximum mount count: 22
Last checked: Mon Feb 22 23:46:22 2010
Check interval: 15552000 (6 months)
Next check after: Sat Aug 21 23:46:22 2010
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: 8b4899b4-fd74-465e-98f2-d4fd27294715
Journal backup: inode blocks
Have you got idea in my outputs?
Thanks
vijay