>
> 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
-----
-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
--
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
