All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Christian Kujau <christian@nerdbynature.de>, linux-ext4@vger.kernel.org
Subject: Re: ext4_ext_check_inode: bad header/extent in inode
Date: Fri, 24 Apr 2009 07:42:01 -0500	[thread overview]
Message-ID: <49F1B399.2040402@redhat.com> (raw)
In-Reply-To: <49F1B24B.7080308@redhat.com>

Eric Sandeen wrote:
> Theodore Tso wrote:
>> On Fri, Apr 24, 2009 at 02:40:58AM -0700, Christian Kujau wrote:
>>> Maybe the repair with 1.41.{3,4} before did something wrong and I should 
>>> use 1.41.5 from the beginning? This issue is somewhat reproducible (given 
>>> the fs holds enough files), so I could start over, corrupt the fs again 
>>> and let e2fsprogs-1.41.5 do the whole job.
>> I doubt it; the problem was that the repair performed by e2fsck 1.41.3
>> was simply imcomplete.  You can try to reproduce the corrupted
>> filesystem again, but it should result in the same result.
>>
>> Note that because there was garbage written into the inode table,
>> there was going to be data loss; there's not much that can be done
>> about that.  This just simple does a better job cleaning up after the
>> mess, that's all.
>>
>> 						- Ted
>>
> 
> But it's still got errors:
> 
> it fixed up inodes 12042, 12207, 12249 in lost+found plus "12090
> (/t/#12090)" (?)
> 
> but post-mount:
> 
> sid:~# mount -t ext4 /dev/md0 /mnt/md0
> sid:~# ls -la /mnt/md0/lost*
> ls: cannot access /mnt/md0/lost+found/#12042: Input/output error
> ls: cannot access /mnt/md0/lost+found/#12207: Input/output error
> ls: cannot access /mnt/md0/lost+found/#12249: Input/output error
> total 20
> c????????? ? ?    ?        ?            ? #12042
> s????????? ? ?    ?        ?            ? #12207
> s????????? ? ?    ?        ?            ? #12249
> drwx------ 2 root root 16384 Apr 23 21:16 .
> drwxr-xr-x 5 root root  4096 Apr 23 21:15 ..
> 
> Christian, is there anything in dmesg along with it this time?

For what it's worth, it seems to repair it ok for me, or at least I'm
not getting your errors:

[root@inode test]# mount -o loop md0_e2i mnt/
[root@inode test]# ls -la mnt/lost*
total 20
drwx------. 2 root       root       16384 2009-04-23 14:16 .
drwxr-xr-x. 5 root       root        4096 2009-04-23 14:15 ..
c--S--s-w-. 1 4232184840 4232201271  8, 0 1970-01-13 00:41 #12042
sr-xrwSr--. 1 4229628009 4228087921     0 1976-03-19 08:28 #12207
sr-xrwSr--. 1 4229628009 4228087921     0 1976-03-19 08:28 #12249




-Eric

  reply	other threads:[~2009-04-24 12:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 12:15 ext4_ext_check_inode: bad header/extent in inode Christian Kujau
2009-04-23 12:50 ` Eric Sandeen
2009-04-23 19:04   ` Christian Kujau
2009-04-23 20:40     ` Theodore Tso
2009-04-23 22:15       ` Christian Kujau
2009-04-24  3:20         ` Theodore Tso
2009-04-24  7:09           ` Andreas Dilger
2009-04-24 11:58             ` Theodore Tso
2009-04-24 20:09               ` Andreas Dilger
2009-04-24  8:57           ` Christian Kujau
2009-04-24  9:40             ` Christian Kujau
2009-04-24 12:00               ` Theodore Tso
2009-04-24 12:36                 ` Eric Sandeen
2009-04-24 12:42                   ` Eric Sandeen [this message]
2009-04-24 20:21                   ` Christian Kujau
2009-04-24 20:34                     ` Eric Sandeen
2009-04-24 20:59                       ` Theodore Tso
2009-04-24 22:54                         ` [PATCH] ext4: Do not try to validate extents on special files Theodore Ts'o
2009-04-24 21:02                       ` ext4_ext_check_inode: bad header/extent in inode Christian Kujau
2009-04-24 21:23                         ` Eric Sandeen
2009-04-24 20:41                 ` Christian Kujau
2009-04-23 20:51     ` Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49F1B399.2040402@redhat.com \
    --to=sandeen@redhat.com \
    --cc=christian@nerdbynature.de \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.