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 19:22:23 +0800	[thread overview]
Message-ID: <ccdf8c94-3fae-8c04-7b4f-b5bb7546ed06@gmx.com> (raw)
In-Reply-To: <CAKuJGC-NaE3J2tu+HEED5fkBs5C=kkkrJqb0QfkTtpdmEdSn9Q@mail.gmail.com>


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



On 2017年11月24日 18:15, Lakshmipathi.G wrote:
>>
>> No, it's not about btrfs-image itself, the flag is introduced long long
>> long way ago.
>>
> Okay.
> 
>> It's about kernel change which doesn't allow image with such flag to be
>> mounted AFAIK.
> 
> No luck yet! It works on 4.14.0

The same dmesg result as I, so I didn't see any problem here.

To make it clear, what kernel config and commit are you using when the
test fails?

In my test, if I use the david/for-4.15 branch, it will fails to umount
the fs, due to the known bug if you enabled
CONFIG_BTRFS_FS_CHECK_INTEGRITY (you reported it first).
And for any upstream kernel version like v4.14-rc7 or v4.14, not problem
at all.

BTW, the btrfs-progs version should not affect, since all the problem is
about kernel failing to mount.

Despite that (either disable that option or apply the patch I submitted)
I can't reproduce the bug you reported (which fails to mount the fs).

Thanks,
Qu
> -----
> -bash-4.4$ sudo make TEST=021\* test-misc
>     [TEST]   misc-tests.sh
>     [TEST/misc]   021-image-multi-devices
> -bash-4.4$ sudo dmesg
> [  162.635824] BTRFS: device fsid f0c92f1b-c1ba-4576-8a07-8ce4f7b5bacd
> devid 1 transid 5 /dev/loop0
> [  162.672952] BTRFS: device fsid f0c92f1b-c1ba-4576-8a07-8ce4f7b5bacd
> devid 2 transid 5 /dev/loop1
> [  162.692848] BTRFS info (device loop1): disk space caching is enabled
> [  162.695725] BTRFS info (device loop1): has skinny extents
> [  162.698003] BTRFS info (device loop1): flagging fs with big metadata feature
> [  162.701643] BTRFS info (device loop1): creating UUID tree
> [  163.792851] BTRFS warning (device loop0): unrecognized super flag:
> 17179869184
> [  163.796350] BTRFS info (device loop0): disk space caching is enabled
> [  163.807644] BTRFS info (device loop0): has skinny extents
> [  163.811613] BTRFS info (device loop0): checking UUID tree
> [  163.841625] BTRFS error (device loop0): 1 errors while writing supers
> [  163.845457] BTRFS: error (device loop0) in write_all_supers:3709:
> errno=-5 IO failure (1 errors while writing supers)
> [  163.851520] BTRFS info (device loop0): forced readonly
> [  163.855184] BTRFS warning (device loop0): Skipping commit of
> aborted transaction.
> [  163.859121] BTRFS: error (device loop0) in
> cleanup_transaction:1873: errno=-5 IO failure
> [  163.862577] BTRFS info (device loop0): delayed_refs has NO entry
> [  163.865623] BTRFS error (device loop0): commit super ret -5
> [  163.868303] BTRFS error (device loop0): cleaner transaction attach
> returned -30
> -bash-4.4$ uname -a
> Linux ip-172-31-33-196.us-west-2.compute.internal 4.14.0 #1 SMP Fri
> Nov 24 09:48:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> -----
> 
> Cheers,
> Lakshmipathi.G
> http://www.giis.co.in http://www.webminal.org
> 


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

  reply	other threads:[~2017-11-24 11:22 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
2017-11-24 10:15               ` Lakshmipathi.G
2017-11-24 11:22                 ` Qu Wenruo [this message]
     [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=ccdf8c94-3fae-8c04-7b4f-b5bb7546ed06@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.