All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Lakshmipathi.G" <lakshmipathi.g@gmail.com>
Cc: btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: misc/021-image-multi-devices fails on latest btrfs-devel/misc-next
Date: Fri, 24 Nov 2017 16:29:35 +0800	[thread overview]
Message-ID: <19a5ec80-3860-20b8-cb12-fcb41b21dc00@gmx.com> (raw)
In-Reply-To: <CAKuJGC-SRh=hrF6uo0vRuQd5=61CbPe-mSpuwMA1DcStihY=dg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2549 bytes --]



On 2017年11月24日 16:20, Lakshmipathi.G wrote:
> Okay thanks for the details on btrfs-image. I was about to try with
> previous version of
> btrfs-image.

No, it's not about btrfs-image itself, the flag is introduced long long
long way ago.

It's about kernel change which doesn't allow image with such flag to be
mounted AFAIK.

Thanks,
Qu

> 
> I'll use v4.14 (https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.14.tar.xz)
> and check
> again.
> 
> ----
> Cheers,
> Lakshmipathi.G
> http://www.giis.co.in http://www.webminal.org
> 
> 
> On Fri, Nov 24, 2017 at 1:36 PM, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>>
>> On 2017年11月24日 15:47, Lakshmipathi.G wrote:
>>> Hi Qu,
>>>
>>> I'm using btrfs-progs devel branch. mount command is failing with misc/021.
>>> When I tried to manually mount it. dmesg shows  "unrecognized super
>>> flag: 17179869184"
>>> and interestingly "df -h" shows 16E as available!
>>
>> That flag is meta dump flag, any image recovered from btrfs-image should
>> have that flag.
>>
>> 16E may also related to that, but not a big problem as btrfs-image
>> result should only be used by developers, and all its data is wiped out.
>> (Maybe one day we will not allow RW mount for such image)
>>
>>
>> The problem happens when you try to mount the image, there may be some
>> new commits doing more restrict check for rw mount in devel branch.
>>
>> Would you please try v4.14 kernel?
>>
>> Thanks,
>> Qu
>>
>>>
>>> https://asciinema.org/a/4JGYg7YGQz1PHtdBRJ6AVw0fh
>>>
>>> Let me check further.
>>> ----
>>> Cheers,
>>> Lakshmipathi.G
>>> http://www.giis.co.in http://www.webminal.org
>>>
>>>
>>> On Fri, Nov 24, 2017 at 9:55 AM, Lakshmipathi.G
>>> <lakshmipathi.g@gmail.com> wrote:
>>>> Hi Qu,
>>>>
>>>> I'm using the same instance. Let me check again with and without the
>>>> commits list on Nov-23
>>>> (https://github.com/kdave/btrfs-devel/commits/misc-next) and get back
>>>> with results.
>>>>
>>>> ----
>>>> Cheers,
>>>> Lakshmipathi.G
>>>> http://www.giis.co.in http://www.webminal.org
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]

  reply	other threads:[~2017-11-24  8:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18  7:29 misc/021-image-multi-devices fails on latest btrfs-devel/misc-next Lakshmipathi.G
2017-11-23  3:16 ` Lakshmipathi.G
2017-11-24  1:18   ` Qu Wenruo
2017-11-24  4:25     ` Lakshmipathi.G
2017-11-24  7:47       ` Lakshmipathi.G
2017-11-24  8:06         ` Qu Wenruo
2017-11-24  8:20           ` Lakshmipathi.G
2017-11-24  8:29             ` Qu Wenruo [this message]
2017-11-24 10:15               ` Lakshmipathi.G
2017-11-24 11:22                 ` Qu Wenruo
     [not found]                   ` <CAKuJGC930Nm4pNqA+xH5HRbx0pWBKR4KXnS32hP+NYSdvO7arA@mail.gmail.com>
2017-11-24 11:50                     ` Qu Wenruo
2017-11-24 12:05                       ` Lakshmipathi.G
2017-11-26 11:36                         ` Lakshmipathi.G

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=19a5ec80-3860-20b8-cb12-fcb41b21dc00@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=lakshmipathi.g@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.