On 08/14/2014 06:28 PM, Marc MERLIN wrote: > On Thu, Aug 14, 2014 at 06:03:09PM -0400, Chris Mason wrote: >> At least I'll get to buy you a beer this time. > > Haha, no worries :) > >> Lets just see if the log root is the only problem. This will get you >> through btrfs-zero-log > > It sure did, thanks much for the patch. > It output absolutely nothing instead of the wanted got lines it usually > spits out, and the filesystem mounted without problems. > > I'll add this better btrfs-zero-log in my initrd for next time. > > Would it be ok to modify btrfs-zero-log to simply remove the return -EIO > line? > > Does it really matter whether it can setup the log root tree when it's being > asked to nuke the log? Yes, btrfs-zero log doesn't need that root to be read. I'll fix it up, really glad it worked for you. -chris -- 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
