Re: fsck: i_blocks is xxx should be yyy on ext3

Helge Hafting <[email protected]> wrote:
>
>  Today I rebooted into 2.6.16-rc2-mm1.  Fsck checked a "clean" ext3 fs,
>  because it was many mounts since the last time.
> 
>  I have seen that many times, but this time I got a lot of
>  "i_blocks is xxx, should be yyy fix?"
> 
>  In all cases, the blocks were fixed to a lower number.

Yes, thanks.  It's due to the ext3_getblocks() patches in -mm.  I can't
think of any actual harm which it'll cause.

To reproduce:

mkfs
mount
dbench 32
<wait 20 seconds>
killall dbench
umount
fsck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: fsck: i_blocks is xxx should be yyy on ext3
    • From: Mingming Cao <[email protected]>

• References:
  • fsck: i_blocks is xxx should be yyy on ext3
    • From: Helge Hafting <[email protected]>

• Prev by Date: [PATCH/RFC] arch/x86_common: more formal reuse of i386+x86_64 source code
• Next by Date: Re: [PATCH/RFC] arch/x86_common: more formal reuse of i386+x86_64 source code
• Previous by thread: fsck: i_blocks is xxx should be yyy on ext3
• Next by thread: Re: fsck: i_blocks is xxx should be yyy on ext3
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]