From: Zheng Liu <gnehzuil.liu@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: [regression][dev] IO failure is hitted by xfstest 083
Date: Thu, 11 Apr 2013 20:17:40 +0800 [thread overview]
Message-ID: <20130411121740.GA3388@gmail.com> (raw)
Hi all,
I run xfstests #083 against dev branch of ext4 tree, and a regression is
hitted. This file system is with bigalloc feature. The error msg looks
like the following. I found the regression is introduced by this
commit: d7ddbabdf6e771b9793aaa7da9c3e9dc4cd376ab
ext4: move quota initialization out of inode allocation transaction
But I doubt this isn't the root cause.
Regards,
- Zheng
wenqing: run xfstest 083
kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: acl,user_xattr
kernel: EXT4-fs error (device sda2) in ext4_reserve_inode_write:4955: IO failure
kernel: EXT4-fs error (device sda2) in ext4_reserve_inode_write:4955: IO failure
kernel: EXT4-fs error (device sda2) in ext4_reserve_inode_write:4955: IO failure
kernel: EXT4-fs warning (device sda2): ext4_evict_inode:257: couldn't mark inode dirty (err -5)
kernel: EXT4-fs warning (device sda2): ext4_evict_inode:257: couldn't mark inode dirty (err -5)
kernel: EXT4-fs warning (device sda2): ext4_evict_inode:257: couldn't mark inode dirty (err -5)
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 1592
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 699
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 1592
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 1592
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 1592
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 1592
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 699
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 699
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: JBD2: Spotted dirty metadata buffer (dev = sda2, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
kernel: EXT4-fs error (device sda2): ext4_free_inode:319: comm fsstress: bit already cleared for inode 1592
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
kernel: EXT4-fs error (device sda2) in __ext4_new_inode:962: IO failure
reply other threads:[~2013-04-11 12:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130411121740.GA3388@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=linux-ext4@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.