> Did you manage to capture that output at all? (A photo would do). Not yet, i am still on recovery from backup, that may take some time. If i am done, i'll re-attach the broken btrfs system and dump some information. It shouldn't be a big problem to redirect the kernel messages to a file. > What kernel version are you running? (anything earlier than 2.6.39 > is probably considered too old for comfort) 3.0.0 is my current running kernel. Due to the fact that i created the whole btrfs filesystem around two weeks before i think i also created it with 3.0.0 but i am not sure. > btrfsck doesn't generally achieve much at the moment. However, having > mount hang is quite odd. It usually either succeeds, or causes a > kernel oops (if the latter has already happened, then *subsequent* > mount attempts may hang, but the original oops is still of interest) > It'd be good if you have the time to try to reproduce this, > particularly with the latest kernels (3.0 or 3.1-rcX) I can, with 3.0.0. Give me some hours of recovery :) Björn -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
