Am Montag, 26. März 2012 schrieb Skylar Burtenshaw: > Fajar A. Nugraha <list <at> fajar.net> writes: > > Didn't Chris' last response basically say "use kernel 3.2 or newer, > > mount the fs (possibly with -o ro), and copy the data elsewhere"? > > Why yes, yes it did actually. I appreciate your spotlighting it, just > in case I somehow managed to miss it, though. > > > Have you done that? > > I have. In fact, in my first message, I stated that in all kernels up > to present 3.2 kernels, I get several minutes of disk churning, then a > stack trace. Also present in my messages is the fact that the > filesystem will not mount, as well as data output from the recovery > program etc which fail to recognize things in the filesystem that they > require in order to fix it. Did you have something you wished to > suggest, in order to help me? If so, I'd gladly listen to any proposed > ideas. Since I didn´t found any explicit mention on it: Did you try btrfs-zero-log on the partition prior to mounting it? All of my BTRFS will not mount after sudden write interruption cases have been solved by it. Except one with a BTRFS RAID 0 with lots of 2 TB drives at a time where I didn´t know about btrfs-zero-log. Maybe it would have helped there, too. Of course I could be completely off track and this could be a completely different issue. -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- 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
