On Mon, Mar 26, 2012 at 3:49 PM, Skylar Burtenshaw <[email protected]> wrote: > 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 you apprently tried "-o ro" (which I missed), then my last suggestion is probably kernel 3.3 with "-o ro". just in case :) -- Fajar -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
