On Thu, 2007-09-27 at 07:53 +0200, David Losada Gacio wrote: > Dear Dave, > I hope you have enough data to fix, I'm sorry if you have lost the > test case with me. It was a hardware failure; the HD went to sleep for > its own a lot of times; sometimes it didn't wake up until 3 or 4 > minutes later.
The stack trace pointed right to the line of code where it was crashing, and it was easy enough to see that reading bad data from the journal could lead to a bad memory access. It's just a matter of determining the best way to sanity check the data, and aborting the journal replay cleanly. > The HD runs OK, but after some hours (even doing nothing) he feels > it needs sleep ;-), in an ocassion I had to shutdown the computer > because his sleeping last too long; so probably some journal data get > corrupted? I'm not sure exactly how the data got corrupted. Maybe one of the last writes before the hd shut down had errors. I could only guess. > > If I can help in something please tell me (I'm not a programmer but > I learn fast). I have enough information to fix this bug. Thanks for your help. > > Thank you, and regards from Spain, > > David Losada Thanks, Shaggy -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
