[<prev] [next>] [day] [month] [year] [list]
Message-ID: <bug-95571-13602@https.bugzilla.kernel.org/>
Date: Wed, 25 Mar 2015 15:18:28 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 95571] New: ext4 fs corruption on power-cut while running
fsstress
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@...nel-bugs.osdl.org
Reporter: ionut.trandafir12@...il.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.
--
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
Powered by blists - more mailing lists