 | | | Problems with fsck | Problems with fsck 2005-07-15 - By F?bio Mendon?a Albuquerque Cunha
Back
Hello Guys,
I am with a huge problem with a server here.
I have a contingency file server with RAID 5 ...
I replace a disk that failed yesterday .... The RAID was rebuild ... Then I
umount the disk and run this command
#fsck.ext3 -vfy /dev/sda1
At the final output I have this :
Inode 29294598 has illegal block(s). Clear? yes
Illegal block #12 (879226656) in inode 29294598. CLEARED.
Illegal block #13 (3315620004) in inode 29294598. CLEARED.
Illegal block #14 (2340312175) in inode 29294598. CLEARED.
Illegal block #15 (3564345759) in inode 29294598. CLEARED.
Illegal block #16 (510048934) in inode 29294598. CLEARED.
Illegal block #17 (2568278150) in inode 29294598. CLEARED.
Illegal block #18 (538064865) in inode 29294598. CLEARED.
Illegal block #19 (2530322371) in inode 29294598. CLEARED.
Illegal block #20 (3624553377) in inode 29294598. CLEARED.
Illegal block #21 (4055744104) in inode 29294598. CLEARED.
Illegal block #22 (2167778488) in inode 29294598. CLEARED.
Too many illegal blocks in inode 29294598.
Clear inode? yes
Restarting e2fsck from the beginning...
Group descriptors look bad... trying backup blocks...
fsck.ext3: Invalid argument while checking ext3 journal for /dev/sda1
Well, I try to run the same command again and I see this :
#fsck.ext3 -vfy /dev/sda1
e2fsck 1.27 (8-Mar-2002 (See http://Mar-2002.ora-code.com))
Group descriptors look bad... trying backup blocks...
e2fsck: A block group is missing an inode table while checking ext3 journal for
/dev/sda1
This message make me nervous, so I run tune2fs:
# tune2fs -l /dev/sda1
tune2fs 1.27 (8-Mar-2002 (See http://Mar-2002.ora-code.com))
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 7b5ebdf0-a2bf-4c0f-aef1-85a21199392f
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype sparse_super
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 29310976
Block count: 58611136
Reserved block count: 2930556
Free blocks: 11312643
Free inodes: 28526893
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
Last mount time: Thu Feb 22 10:30:04 2001
Last write time: Thu Feb 22 17:54:18 2001
Mount count: 5
Maximum mount count: 34
Last checked: Tue Jul 12 12:20:49 2005
Check interval: 15552000 (6 months)
Next check after: Sun Jan 8 13:20:49 2006
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
Then, I try to mount the filesystem :
# mount -t ext3 /dev/sda1 /backup
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
or too many mounted file systems
The fdisk returns me :
# fdisk -l
Disk /dev/sda: 255 heads, 63 sectors, 29187 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 29187 234444546 8e Linux LVM -> This is my RAID
5 !!!!!
Disk /dev/hda: 255 heads, 63 sectors, 1823 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 778 6144862+ 83 Linux
/dev/hda3 779 811 265072+ 82 Linux swap
/dev/hda4 812 1823 8128890 f Win95 Ext'd (LBA)
/dev/hda5 812 1823 8128858+ 83 Linux
[root@(protected) root]# df -H
Filesystem Size Used Avail Use% Mounted on
/dev/hda5 8.2GB 983MB 6.7GB 13% /
/dev/hda1 103MB 9.5MB 88MB 10% /boot
none 56MB 0 56MB 0% /dev/shm
/dev/hda2 6.2GB 137MB 5.7GB 3% /var
Where is my mistake ??? How can I clean this filesystem and, the most important
, how can I mount this filesystem.
Please, someone could help me with this ???
Regards.
InfraNet Tecnologia
F?bio M. A. Cunha
(55 11) 5542-0941 ramal 22
(55 11) 8456-5283
www.infranetsp.com.br
www.fsf.org
--
Shrike-list mailing list
Shrike-list@(protected)
https://www.redhat.com/mailman/listinfo/shrike-list
|
|
|