system hangs after deleting bad file

Hallo,

next problem (sorry):

my cluster of 3 2-TByte-disks has some damaged files. When I try to delete the directory entries with the "midnight commander" (via "putty", over the LAN) then "mc" hangs. Killing the putty session and opening (via "putty") a new "mc" window shows that the directory entry doesn't exist - looks good.

Mountpoint is "/mnt/btr".

lsof /mnt/btr

still shows a "mc" entry which I can't remove with "killall -9 mc" or "kill -9 <mc-PID>".

And more bad:

reboot

doesn't work,

Ctrl Alt Delete

(on the machine, not over LAN) doesn't work too.

I have to restart the machine via main power switch - no good job.

Viele Gruesse!
Helmut

Hello Helmut!

I'm having the same observation currently: There are bad files in my $HOME and I can't delete them because it makes the kernel ooops. I tried Josef's repair program but it fails an assertion. What's your kernel backtrace? Did you try the repair program? Maybe we really got the same problem and could combine efforts? I filed an issue here:

https://github.com/josefbacik/btrfs-progs/issues/1

Hello,
I had a similar problem.

Some files (2-3) got corrupted in my /home subvolume for no apparent reason. Trying to access the files gives kernel oops. Sometimes it freezes the machine, sometimes I am back to my console without any problems.

Then I switched to the latest 3.1rc and freezes were gone (though I still had the kernel oops).

(I did not try the repair program fearing that it would do more bad than good. After all, my / subvolume was fine and i still could mount /home)

But to tackle the problems with corrupted files I had to create a new subvolume for /home, tranfer the files from the old one (minus the corrupted files) and delete the old subvolume.

Though still btrfsck would give me errors trying to access some inode. But I could mount and use all my subvolumes with no problems.

Then... I re-created btrfs with the latest btrfs-tools and installed the latest 3.1rc from the very beginning.

So far, it is working fine and the situation with disk I/O has greatly improved. I think you may want to try to upgrade to the latest 3.1rc and at the very least you (hopefully) should not be getting hard freezes any more.

best
~dima

Hallo, dima,

Du meintest am 24.10.11:

[system hangs]

I'll try in some hours ... I've just seen kernel 3.1 has been released.

Viele Gruesse!
Helmut