David Greaves wrote: This isn't a regression. I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it). I tried 2.6.22-rc4 (with Tejun's patches) to see if it had improved - no
Verrry interesting. What you were seeing was an XFS shutdown occurring because the free space btree was corrupted. IOWs, the process of suspend/resume has resulted in either bad data being written to
David Robinson wrote: David Greaves wrote: This isn't a regression. I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it). I tried 2.6.22-rc4 (with Tejun's patches) to see i
OK, just an quick ack When I resumed tonight (having done a freeze/thaw over the suspend) some libata errors threw up during the resume and there was an eventual hard hang. Maybe I spoke to soon? I'm
David Greaves wrote: David Robinson wrote: David Greaves wrote: This isn't a regression. I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it). I tried 2.6.22-rc4 (with Teju
Hmm, so XFS writes to disk even when its threads are frozen? Could you add that to the XFS threads if it is really required? They do know that they are being frozen for suspend. Pavel -- (english) h
Well, do you remember the workqueues? They are still nonfreezable. Greetings, Rafael -- "Premature optimization is the root of all evil." - Donald Knuth
They issue async I/O before they sleep and expects processing to be done on I/O completion via workqueues. We don't suspend the threads on a filesystem freeze - they continue run. A filesystem freeze
David Greaves wrote: This isn't a regression. I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it). I tried 2.6.22-rc4 (with Tejun's patches) to see if it had improved - no
Verrry interesting. What you were seeing was an XFS shutdown occurring because the free space btree was corrupted. IOWs, the process of suspend/resume has resulted in either bad data being written to
David Robinson wrote: David Greaves wrote: This isn't a regression. I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it). I tried 2.6.22-rc4 (with Tejun's patches) to see i
OK, just an quick ack When I resumed tonight (having done a freeze/thaw over the suspend) some libata errors threw up during the resume and there was an eventual hard hang. Maybe I spoke to soon? I'm
David Greaves wrote: David Robinson wrote: David Greaves wrote: This isn't a regression. I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it). I tried 2.6.22-rc4 (with Teju
Hmm, so XFS writes to disk even when its threads are frozen? Could you add that to the XFS threads if it is really required? They do know that they are being frozen for suspend. Pavel -- (english) h
Well, do you remember the workqueues? They are still nonfreezable. Greetings, Rafael -- "Premature optimization is the root of all evil." - Donald Knuth
They issue async I/O before they sleep and expects processing to be done on I/O completion via workqueues. We don't suspend the threads on a filesystem freeze - they continue run. A filesystem freeze