Filesystem corrupt after renaming snapshots.

2011-08-10 Thread Ralph Loader
Hi, Recently I suffered from a badly corrupted btrfs filesystem. I had several snapshots in /snap that I moved into / (using /bin/mv). After that, attempting to access the ls the snapshot resulted in the ls process hanging. There were syslog messages: Aug 7 20:56:42 i kernel: [ 111.882816]

Locking backtrace

2010-12-23 Thread Ralph Loader
Hi, The following two stacktraces appeared in my syslog (are they of any use?). The "possible recursive locking" occured around the end of untaring a 4gig tar ball. I think the other one occurred during a 'yum upgrade'. Cheers, Ralph. Dec 24 20:26:01 i kernel: [113505.458570] Dec 24 20:26:0

Ooops mounting non existant subvolume.

2010-10-22 Thread Ralph Loader
Hi, If I attempt to mount a non-existant subvolume, e.g., mount -o subvol=1 /dev/sda6 /mnt then I get an an oops (see end of message). /dev/sda6 is my root filesystem, 'btrfs sub list /' gives ID 331 top level 5 path snap/rawhide ID 341 top level 5 path snap/20101014 ID 342 top level 5 path sn