I have an apple Xserve RAID attached to a Linux Box, serving one Raided LUN of 2500Gigs, it was functional until the box crashed. When I hard booted it, even though it mounted the FS, I've been unable to access it. Cd-ing to any of its directories gives "Input/Output error". The ls ?la on the FS shows "?" for every field with no permission information. The /var/log/messages is flooded with: Feb 1 10:12:21 *HOSTNAME* kernel: EXT3-fs error (device sda1): ext3_get_inode_loc: unable to read inod e block - inode=178356225, block=356712450 An e2fsck gives e2fsck 1.35 (28-Feb-2004) /xraid: recovering journal The filesystem size (according to the superblock) is 610476016 blocks The physical size of the device is 73605104 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? It seems like the partition table is corrupted and not the superblock, and if so, what would be the right way of going about it?! I am reluctant to answer no to the abort question of e2fsck to try to fix it. Or should I -M -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20070201/055b7ad8/attachment.htm>
On Thu, 1 Feb 2007, Marco Polo wrote:> of its directories gives "Input/Output error". The ls ?la on the FS shows > "?" for every field with no permission information. The /var/log/messages is > flooded with: > > Feb 1 10:12:21 *HOSTNAME* kernel: EXT3-fs error (device sda1): > ext3_get_inode_loc: unable to read inode block - inode=178356225, block=356712450hm, are there device related messages in the syslog? "unable to read inode block" sounds like general i/o errors to me.> e2fsck 1.35 (28-Feb-2004)can you try a more current version? e2fsprogs.sf.net is at v1.39> It seems like the partition table is corrupted and not the superblock, and > if so, what would be the right way of going about it?!sorry to repeat myself, but at first I'd make sure that there are no device errors. if this can be ruled out: do you have spare 250GB to backup you (corrupt) fs? if yes - please do, then use the current fsck to try to repair the fs. C. -- BOFH excuse #45: virus attack, luser responsible
On Fri, 2 Feb 2007, Marco Polo wrote:> Feb 2 11:49:15 backup kernel: EXT3-fs warning (device sda1): > ext3_clear_journal_err: Filesystem error recorded from previous mount: > IO failurewell, that's the one spot where it says "io failure". from looking at the other places in fs/ext3/inode.c I cannot tell for sure if they are related to IO errors though...> Feb 2 11:49:15 backup kernel: EXT3-fs warning (device sda1): > ext3_clear_journal_err: Marking fs in need of filesystem check. > Feb 2 11:49:15 backup kernel: EXT3-fs warning: mounting fs with errors, > running e2fsck is recommendedso, mounting succeeds and even recovery is fine. looks like filesystem structure is intact.> Feb 2 11:49:15 backup kernel: SELinux: initialized (dev sda1, type ext3), > uses xattr > Feb 2 11:49:23 backup kernel: EXT3-fs error (device sda1): > ext3_get_inode_loc: unable to read inode block - inode=127238145, > block=254476290...yet e2fsck fails to repair the fs? have you tried the current version? but anyway: since you can mount the fs: try to mount it ro, probably withouth fancy options and try to backup your data if you did not already. btw, which kernel/distribution is this? does a more current kernel help? (it won't help when I/O errors really are to blame) Christian. -- BOFH excuse #153: Big to little endian conversion error