Bug 95571
| Summary: | ext4 fs corruption on power-cut while running fsstress | ||
|---|---|---|---|
| Product: | File System | Reporter: | Ionut Trandafir (ionut.trandafir12) |
| Component: | ext4 | Assignee: | fs_ext4 (fs_ext4) |
| Status: | NEW --- | ||
| Severity: | normal | CC: | szg00000 |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 4.0.0-rc3 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | ext4 fs corruption at power cut | ||
Created attachment 172361 [details] 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.