Thank you all for the quick response! For anyone running into similar issues:
I updated my kernel, and then ran btrfs-zero-log. Everything worked fine, and the drive is mountable with no issues so far. -Jon On Wed, Sep 9, 2015 at 12:27 PM, Roman Mamedov <r...@romanrm.net> wrote: > On Wed, 9 Sep 2015 17:19:51 +0000 > Hugo Mills <h...@carfax.org.uk> wrote: > >> The bug you've hit is almost certainly fixed in more recent >> kernels. I can't recommend stongly enough that you upgrade it (or >> contact your vendor's support department to find out how they will >> support your use of btrfs on a kernel that old). 3.19 is about the >> earliest kernel I'd feel happy about using at this point. > > 3.19 is EOL and is not featured on https://www.kernel.org/ anymore. > > I hope 3.18 is also good enough, for those of us who prefer to stay on a > "longterm" kernel and not jump every time onto a new series only to find out > that it's in fact destined to go into the EOL trashcan. (There's a certain > amount of tinkering with the .config required each time when switching > releases, and I'd like to minimize that). > > -- > With respect, > Roman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
