On Fri, Jul 13, 2012 at 02:23:53PM +0200, Martin Steigerwald wrote: > 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. I'm afraid you probably are -- there's nothing I can see in the stack trace that would indicate that it's falling over in the log tree replay, which is the only thing that btrfs-zero-log would help with. Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- A diverse working environment: Di longer you vork here, di --- verse it gets.
Attachment:
signature.asc
Description: Digital signature
