All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: Theodore Tso <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: [BUG] ext4: i_size, EOFBLOCKS_FS corruption with xfstests 269
Date: Wed, 18 Jul 2012 16:58:11 +0900	[thread overview]
Message-ID: <50066C93.1070006@rs.jp.nec.com> (raw)

Hi,

I got a issue which makes i_size and EOFBLOCKS_FL corrupted
on ext4 with xfstests 269.
In my environment (linux-3.5-rc7), this can be reproduced
once of 10 times trial.

Kernel: 3.5-rc7
Arch: x86_64

Step and log are as bellow, after xfstests 269, e2fsck outputs
i_size and EOFBLOCKS_FL corruption.
Is this an already known issue?

# ./check 269
    FSTYP         -- ext4
    PLATFORM      -- Linux/x86_64 mcds1 3.5.0-rc7
    MKFS_OPTIONS  -- /dev/sdb3
    MOUNT_OPTIONS -- -o acl,user_xattr /dev/sdb3 /mnt/mp2

    269 97s ... [failed, exit status 1] - output mismatch (see 269.out.bad)
    --- 269.out	2012-07-02 10:51:34.000000000 +0900
    +++ 269.out.bad	2012-07-18 14:09:03.000000000 +0900
    @@ -3,3 +3,4 @@
     Run fsstress

     Run dd writers in parallel
    +_check_generic_filesystem: filesystem on /dev/sdb3 is inconsistent (see 269.full)
    Ran: 269
    Failures: 269
    Failed 1 of 1 tests


    # cat 269.full
      (snip)

    e2fsck 1.41.12 (17-May-2010)
    Pass 1: Checking inodes, blocks, and sizes
    Inode 2336, i_size is 625045, should be 1277952.  Fix? no

    Inode 3193 should not have EOFBLOCKS_FL set (size 1928717, lblk 218)
    Clear? no

    Inode 4198 should not have EOFBLOCKS_FL set (size 380389, lblk 73)
    Clear? no


Regards,
Akira Fujita

             reply	other threads:[~2012-07-18  7:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18  7:58 Akira Fujita [this message]
2012-07-18  9:40 ` [BUG] ext4: i_size, EOFBLOCKS_FS corruption with xfstests 269 Lukáš Czerner
2012-07-20  4:49   ` Akira Fujita

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=50066C93.1070006@rs.jp.nec.com \
    --to=a-fujita@rs.jp.nec.com \
    --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.