Bastian Blank wrote: > > [...] > > Log from the fsck run? Again, I don't have an actual file, just written notes. I can give you the list of orhan inodes, but the bitmaps were a bit much to write down. Any thoughts on how to capture this stuff next time this happens (it was the second time alread, I had neglegted to mention that)?
> Some of the differences are normal if the journal > got aborted. But overall this looks like bad hardware, most likely > memory. I'll try running memtester and/or memtest86 to check this. -- Matijs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
