On 04/06/2009 09:39 PM, Tejun Heo wrote:
> Hello,
>
> Niel Lambrechts wrote:
>   
>> On 04/06/2009 12:09 PM, Tejun Heo wrote:
>>     
>>>> Will the fix naturally make its way into the mainline kernel, or is
>>>> there any extra debugging/testing I can help with?
>>>>     
>>>>         
>>> Well, the problem is the debug patch doesn't actually do anything
>>> other than printing out messages.  It could be that the problem is
>>> timing dependent (which is likely anyway).  You still can reporduce
>>> the problem with the patch, right?
>>>   
>>>       
>> Heh? You provided two patches, with the last one you said:
>>     
>
> Yeah, the second one actually only added printks to see whether that's
> the case.  No behavior change.
>
>   
>>> Strange.  Maybe IO commands are getting through while the sdev is
>>> still in quiesce state?  Can you please repeat the test with the
>>> attached patch?
>>>       
>> With the latter, I have not encountered the original problem i.e. any
>> severe EXT4 corruption again, not in 2.6.29 and not in 2.6.29.1.
>>     
>
> Eh... so, we're definitely seeing something which is dependent on
> timing.
>
>   
>> Do I also need to try the last patch without any debugging messages?
>>     
>
> Then there will be nothing left.  :-) Can you please try the attached
> patch?  It's still only debug messages but lighter; hopefully, it
> won't mask the problem.
>   
Sorry, my bad - I assumed the 2nd patch actually made a functional
difference... :)

Here is the output on 2.6.29.1 with your new patch - still nothing
serious happening, resume still seems okay!

cheers
Niel