Hide Forgot
Description of problem: Hard shutdowning of a machine with fs operations on sata caused fs corruption when I did power failure testing for rhel6.1(https://tcms.engineering.redhat.com/run/18635/?from_plan=1232), I found: For the test scenario "nobarriers enabled and local write cache on" with workload "fs_mark -d /media/sdb/dir -s 51200 -n 4096 -L 10 -r 8 -D 128" (without the option -S 0), I have tested this for three times and they all failed. Seems RHEL6.1 Ext4 is risky in this scenario. Logs are attached. Version-Release number of selected component (if applicable): RHEL6.1-20110323.1 Kernel 2.6.32-125.el6.x86_64 How reproducible: At times Steps to Reproduce: 1.Please view https://tcms.engineering.redhat.com/run/18635/?from_plan=1232 and the case "power testing: on SATA disk". Actual results: Filesystems corruptions found. Expected results: Filesystems are sane. Additional info:
Created attachment 489289 [details] When fs corruptions were found for the first time, its dmesg.
Created attachment 489290 [details] When fs corruptions were found for the first time, its test log.
Created attachment 489291 [details] When fs corruptions were found for the second time, its dmesg.
Created attachment 489292 [details] When fs corruptions were found for the second time, its test log.
Created attachment 489293 [details] When fs corruptions were found for the third time, its dmesg.
Created attachment 489294 [details] When fs corruptions were found for the third time, its test log.
Hi Igor, With nobarriers and write cache enabled, this is expected behavior. Unless I misunderstand the setup, this should be closed as NOTABUG. Thanks!
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.