On Sat, Aug 9, 2014 at 9:32 AM, Andy Smith <andy@xxxxxxxxxxxxxx> wrote: > Hello, > > On Sat, Aug 09, 2014 at 01:38:34PM +1000, Russell Coker wrote: >> On Fri, 8 Aug 2014 16:35:29 Jose Ildefonso Camargo Tolosa wrote: >> > Then, after reading here and there, decided to try to use a newer >> > kernel, tried 3.15.8. Well, it is still mounting after ~16 hours, and >> > I got messages like these at first: >> >> I recommend trying a 3.14 kernel. I had ongoing problems with kernels before >> 3.14 which included infinite loops in kernel space. Based on reports on this >> list I haven't been inclined to test 3.15 kernels. But 3.14 has been working >> well for me on many systems. > > I'm in a similar position with a filesystem that won't mount except > read-only, but am already on 3.14 and am also wondering whether to > try a 3.16 kernel. > > https://bugzilla.kernel.org/show_bug.cgi?id=81981 > > Jose, maybe you could try -oro in the hope of at least getting back > to a read-only mount? Will try 3.14, ro would be "good enough" for me, provided that I can resize the filesystem, if I can do that, I can create a new one, and copy all data (hopefully faster than moving ~11TB of data through the network). -- 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
