On Wed, Jan 11, 2012 at 10:30:39AM +0100, Yamagi Burmeister wrote: > Hello, > I've done some tests to verify that the problem only occures when SU+J > is used, but not SU without J. In fact, I did run the following two > loops on different TTYs in parallel: I also confirm this using a similar technique. The panic is only seen with SU+J and not with just SU. I did a similar cp -R /root /var/tmp ; rm -rf /var/tmp/root and the panic was trigger with dump -0L... I got the panic (again in less than a minute of issuing the dump command) -- I also got the "giving up on dirty" kind of message. I took a picture of the screen -- I am not sure if that helps! http://picpaste.com/11012012519-LF0sWlpw.jpg > Since it's much more likely that the problems described above arrise > when the the filesystem is loaded (for example by the first loop) while > taking the snapshot this looks like some kind of race condition or > something like that. > Earlier I have seen this happen with dump without any high load -- or atleast very minimum -- again with the /var because some logs were written or cronjob was running writing to it. That didnt panic as I indicated in my previous email -- hogged the CPU and forced a power-cycle. Do let me know if I can try something further. Thanks GautamReceived on Wed Jan 11 2012 - 16:42:47 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:23 UTC