From: Dave Jones <davej@redhat.com>
To: Borislav Petkov <bp@alien8.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: EXT4 corruption on Linus latest tree.
Date: Wed, 27 Feb 2013 11:04:46 -0500 [thread overview]
Message-ID: <20130227160446.GA4792@redhat.com> (raw)
In-Reply-To: <20130227155539.GA2638@pd.tnic>
On Wed, Feb 27, 2013 at 04:55:39PM +0100, Borislav Petkov wrote:
> On Wed, Feb 27, 2013 at 10:43:11AM -0500, Dave Jones wrote:
> > Built from a pull around midnight EST last night.
> > (Don't have the git hash, as the source is on the disk that is now inaccessable..)
> >
> > EXT4-fs error (device sdb1): htree_dirblock_to_tree:919: inode #172235804: block 152052301: comm ls: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
> > EXT4-fs error (device sdb1): htree_dirblock_to_tree:919: inode #172235804: block 152052301: comm ls: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
> > EXT4-fs error (device sdb1): htree_dirblock_to_tree:919: inode #172235804: block 152052301: comm ls: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
> > EXT4-fs error (device sdb1): htree_dirblock_to_tree:919: inode #172235381: block 152052288: comm ls: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
> > EXT4-fs error (device sdb1): htree_dirblock_to_tree:919: inode #172228609: block 152051744: comm ls: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0
> >
> > This is a 3TB disk which has 1.9TB used.
> >
> > I can see some files/dirs, but some top level dirs now appear empty.
> >
> > About to reboot back to a safe kernel and fsck.
>
> Hmm, more people triggering something like that:
> http://marc.info/?l=linux-kernel&m=136196926015305&w=2
Yeah, looks similar. The missing files/dirs reappeared when I
booted an older kernel, so it looks like the corruption doesn't
hit the disk. Fsck (1.42.5) didn't find anything either.
Dave
next prev parent reply other threads:[~2013-02-27 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 15:43 EXT4 corruption on Linus latest tree Dave Jones
2013-02-27 15:55 ` Borislav Petkov
2013-02-27 16:04 ` Dave Jones [this message]
2013-02-27 16:32 ` Theodore Ts'o
2013-02-27 16:44 ` Theodore Ts'o
2013-02-27 16:56 ` Dave Jones
2013-02-27 17:07 ` gnehzuil.liu
2013-02-27 18:03 ` Theodore Ts'o
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=20130227160446.GA4792@redhat.com \
--to=davej@redhat.com \
--cc=bp@alien8.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox