<div dir="ltr"><br><br><div class="gmail_quote">2008/8/20 r2d2 <span dir="ltr"><<a href="mailto:r2d2z4j6y8@gmail.com">r2d2z4j6y8@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr">[snip hw error]<br><div class="Ih2E3d"><br>> If you type "dmesg" do you see anything about IO errors, DMA resets, or timeouts?<br></div>I didn't notice anything about IO errors or other errors. As I mentioned, there was "Corrupt dmap page" in /var/log/messages before the filesystem was first damaged.<div class="Ih2E3d">
</div></div></blockquote><div><br>It sounds like your filesystem is hosed, have you tried booting into single user mode and runing fsck over the FS? (rather than just relying on the journal) The lockup when you try and do certain things sounds like FS corruption (maybe it's getting stuck in an endless loop when traversing inodes or something??)<br>
<br>The fact things end up in lost+found suggest this also (as this is where FS recovery code will reattach stuff it finds.)<br><br>fsck is the way to go.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><div class="Ih2E3d"><br>
<br>> Depending on how important your recordings are, I'd suggest buying a new disk and copying<br>
> them off one at a time then you'll find out which is on the broken bits of disk.<br></div>
I will consider buying a new disk. It would be quite difficult to identify the broken bits as the filesystem resides on a logical volume built over 2 software RAID arrays (raid1, 2 disks and raid5, 4 disks). I know this is an awful mess. TV shows and movies are not so important, but I am disappointed : the RAID was inefficient to prevent this kind of problem.<br>
</div></blockquote><div><br>This makes me think it's filesystem corruption even more. The raid gives you a fault tolerant block device, it knows nothing about the data that's on that device, so if your filesystem gets corrupted the raid will quite happily give you redundancy for your broken data.<br>
<br>However, as you have RAID a single failing disc shouldn't cause the kind of issues you're having (or at least not without timing out and degrading the RAID.)<br><br>If it does turn out to be FS corruption you're probably best newfsing, but at the least you should /copy/ rather than move affected files. It stands a slightly better chance of working. (moving files can just alter a few on disc pointers, whereas copying will copy the affected data, so you won't recover corrupted files, but you won't have any files that are corrupted lyring around wating to trip you up.)<br>
<br>Cheers<br><br>Ian<br><br></div></div><br></div>