From: Theodore Tso <tytso@mit.edu>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Weird ext4 bug: 256P used?
Date: Mon, 12 Oct 2009 21:05:18 -0400 [thread overview]
Message-ID: <20091013010518.GA2606@mit.edu> (raw)
In-Reply-To: <94a0d4530910121627j74faac64l29169e17c0b2961b@mail.gmail.com>
On Tue, Oct 13, 2009 at 02:27:48AM +0300, Felipe Contreras wrote:
>
> stat /var/lib/yum/yumdb/s/160f96bb8689bae7bed1f8801385845d47913ace-skype-2.0.0.72-fc5-i586
> File: `/var/lib/yum/yumdb/s/160f96bb8689bae7bed1f8801385845d47913ace-skype-2.0.0.72-fc5-i586'
> Size: 4096 Blocks: 281470681743368 IO Block: 4096 directory
> Device: fe00h/65024d Inode: 141257 Links: 2
> Access: (0755/drwxr-xr-x) Uid: (4294901760/ UNKNOWN) Gid: (16711680/ UNKNOWN)
> Access: 2009-10-12 16:36:22.326920328 +0300
> Modify: 2009-07-27 20:52:23.000000000 +0300
> Change: 2009-07-27 20:52:23.000000000 +0300
OK, I see what's going on. i_blocks_hi is getting set to 0xFFFF.
So I definitely see the bug in e2fsck in not reporitng and fixing the
problem (and I'll fix that). I'm not sure how i_blocks_hi got set to
that value, though; it looks like everything should be doing the right
thing in the latest mainline kernel. What version of the kernel are
you using?
- Ted
next prev parent reply other threads:[~2009-10-13 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 13:51 Weird ext4 bug: 256P used? Felipe Contreras
2009-10-12 22:29 ` Theodore Tso
2009-10-12 23:02 ` Felipe Contreras
2009-10-12 23:12 ` Theodore Tso
2009-10-12 23:27 ` Felipe Contreras
2009-10-13 1:05 ` Theodore Tso [this message]
2009-10-13 2:11 ` Theodore Tso
2009-10-13 11:11 ` Felipe Contreras
2009-10-13 12:13 ` Theodore Tso
2009-10-13 12:18 ` Felipe Contreras
2009-10-13 11:08 ` Felipe Contreras
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=20091013010518.GA2606@mit.edu \
--to=tytso@mit.edu \
--cc=felipe.contreras@gmail.com \
--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 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.