The bug report https://bugzilla.kernel.org/show_bug.cgi?id=14543 also has a script that repeatably creates the read-only effect, but I can not get this script to create the effect here - can anyone create a script that reliably replicates this fault?
Comment #7 From Andrey Vihrov 2009-11-05 09:43:18 -------
Created an attachment (id=23658) [details]
dmesg with ext4 failure
Yes. I was able to trigger it by running two scripts in parallel:
while true; do
echo > test
&& sync
&& rm test
&& sync
|| break ;
done
and
while true; do
for FILE in /sys/class/scsi_host/*/link_power_management_policy; do echo
"min_power" > ${FILE} && echo "max_performance" > ${FILE}; done
&& sleep 1 ;
done
Bugzilla bug #14543 describes a very similar issue involving ata flushing which is RESOLVED and available in patch "libata: retry failed FLUSH if device didn't fail it" which is applied from kernel 2.6.33-rc1 mirror. celinuxforum. org/gitstat/ /commit- detail. php?commit= 6013efd8860bf15 c1f86f365332642 cfe557152f
http://
The bug report https:/ /bugzilla. kernel. org/show_ bug.cgi? id=14543 also has a script that repeatably creates the read-only effect, but I can not get this script to create the effect here - can anyone create a script that reliably replicates this fault?
Comment #7 From Andrey Vihrov 2009-11-05 09:43:18 -------
Created an attachment (id=23658) [details]
dmesg with ext4 failure
Yes. I was able to trigger it by running two scripts in parallel:
while true; do
echo > test
&& sync
&& rm test
&& sync
|| break ;
done
and
while true; do scsi_host/ */link_ power_managemen t_policy; do echo
for FILE in /sys/class/
"min_power" > ${FILE} && echo "max_performance" > ${FILE}; done
&& sleep 1 ;
done