Messages in this thread | | | Date | Tue, 8 Mar 2011 16:22:59 +0100 | Subject | Re: Reiserfs deadlock in 2.6.36 | From | Bastien ROUCARIES <> |
| |
On Tue, Mar 8, 2011 at 3:18 PM, Frederic Weisbecker <fweisbec@gmail.com> wrote: > On Sun, Jan 30, 2011 at 01:08:29AM +0100, Bastien ROUCARIES wrote: >> Le jeudi 23 décembre 2010 04:42:33, Frederic Weisbecker a écrit : >> Hi, >> >> I take me more than two days of testing to reporduce this bugs with trace enabled. My filesystem was quite slow and this bugs seems >> to be timing related. >> >> One patern that trigger this bug is git. Doing a lot of git work of my desktop crash my machine. >> >> Moreover, trying to reproduce this bug lead to data loss. I have rebuilded twice my / partition using --rebuild-tree, and restored >> my home partition three times using backups. >> >> My log is here. >> >> Do you need more information? >> >> Bastien > > You have a first series of hung task report from 19440.852298 to 19440.880024 > then it's followed by the traces and then again with a hung task report at > 19560.880084. But there is only one task stuck in that 2nd report. Did > you report your whole dmesg there or have you cut it? If it's your > whole dmesg then it means the other tasks from the first report have released > from their hung state. So the queued writers have been released by someone > who closed the journal.
I have reported the whole stuff. But because my log need to go to my disk, we could have loss something
> This could confirm the theory that someone has opened the journal and > spent way too much time before releasing it. Or something else. > In any case tell me, there are other tests we can run. >
Ok bastien -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |