linux-ext4 - [regression][dev] IO failure is hitted by xfstest 083

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20130411121740.GA3388@gmail.com>
Date:	Thu, 11 Apr 2013 20:17:40 +0800
From:	Zheng Liu <gnehzuil.liu@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: [regression][dev] IO failure is hitted by xfstest 083

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html