From: Chris Mason <clm@fb.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Austin S Hemmelgarn <ahferroin7@gmail.com>,
<linux-btrfs@vger.kernel.org>, <jbacik@fb.com>,
<takeuchi_satoru@jp.fujitsu.com>
Subject: Re: btrfs-zero-log fails, can't mount FS
Date: Thu, 14 Aug 2014 20:17:02 -0400 [thread overview]
Message-ID: <53ED517E.9010600@fb.com> (raw)
In-Reply-To: <20140814222818.GL27531@merlins.org>
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
next prev parent reply other threads:[~2014-08-15 0:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 16:09 btrfs-zero-log fails, can't mount FS Marc MERLIN
2014-08-14 16:52 ` Austin S Hemmelgarn
2014-08-14 17:27 ` Marc MERLIN
2014-08-14 19:10 ` Chris Murphy
2014-08-14 19:14 ` Marc MERLIN
2014-08-14 22:03 ` Chris Mason
2014-08-14 22:28 ` Marc MERLIN
2014-08-15 0:17 ` Chris Mason [this message]
2014-08-15 4:11 ` Marc MERLIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53ED517E.9010600@fb.com \
--to=clm@fb.com \
--cc=ahferroin7@gmail.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.org \
--cc=takeuchi_satoru@jp.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).