From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 95571] New: ext4 fs corruption on power-cut while running fsstress
Date: Wed, 25 Mar 2015 15:18:28 +0000 [thread overview]
Message-ID: <bug-95571-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=95571
Bug ID: 95571
Summary: ext4 fs corruption on power-cut while running fsstress
Product: File System
Version: 2.5
Kernel Version: 4.0.0-rc3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: ionut.trandafir12@gmail.com
Regression: No
Created attachment 172361
--> https://bugzilla.kernel.org/attachment.cgi?id=172361&action=edit
ext4 fs corruption at power cut
I'm using an Ubuntu-13.10 VM for this testing. Kernel 4.0.0-rc3 compiled from
git and e2fsprogs 1.42.12.
The steps I run:
# mkfs.ext4 /dev/sdb1
# mount -t ext4 -o defaults,barrier=1,noatime /dev/sdb1 /mnt
# fsstress -w -X -d /mnt/fsstress -l 0 -n 100 -p 100 -s urandom
Let it run for 10 sec and then poweroff the virtual machine:
$ vboxmanage controlvm Ubuntu-13.10-server poweroff
After reboot, I run:
# fsck.ext4 -vpf /dev/sdb1
This fails with exit code 4, 2 out of 10 runs. The fail log is attached.
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2015-03-25 15:18 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=bug-95571-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).