* cannot mount read-write because of unsupported optional features (2)
@ 2016-11-01 4:46 Tobias Holst
2016-11-01 5:24 ` Qu Wenruo
0 siblings, 1 reply; 4+ messages in thread
From: Tobias Holst @ 2016-11-01 4:46 UTC (permalink / raw)
To: linux-btrfs@vger.kernel.org
Hi
I can't mount my boot partition anymore. When I try it by entering
"mount /dev/sdi1 /mnt/boot/" I get:
> mount: wrong fs type, bad option, bad superblock on /dev/sdi1,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
"dmesg | tail" gives me:
> BTRFS info (device sdi1): using free space tree
> BTRFS info (device sdi1): has skinny extents
> BTRFS error (device sdi1): cannot mount read-write because of unsupported optional features (2)
> BTRFS: open_ctree failed
I am using an Ubuntu 16.10 Live CD with Kernel 4.8 and btrfs-progs v4.8.2.
"btrfs inspect-internal dump-super /dev/sdi1" gives me the following:
> superblock: bytenr=65536, device=/dev/sdi1
> ---------------------------------------------------------
> csum_type 0 (crc32c)
> csum_size 4
> csum 0x0f346b08 [match]
> bytenr 65536
> flags 0x1
> ( WRITTEN )
> magic _BHRfS_M [match]
> fsid 67ac5740-1ced-4d59-8999-03bb3195ec49
> label t-hyper-boot
> generation 64
> root 20971520
> sys_array_size 129
> chunk_root_generation 43
> root_level 1
> chunk_root 12587008
> chunk_root_level 0
> log_root 0
> log_root_transid 0
> log_root_level 0
> total_bytes 2147483648
> bytes_used 102813696
> sectorsize 4096
> nodesize 4096
> leafsize 4096
> stripesize 4096
> root_dir 6
> num_devices 1
> compat_flags 0x0
> compat_ro_flags 0x3
> incompat_flags 0x34d
> ( MIXED_BACKREF |
> MIXED_GROUPS |
> COMPRESS_LZO |
> EXTENDED_IREF |
> SKINNY_METADATA |
> NO_HOLES )
> cache_generation 53
> uuid_tree_generation 64
> dev_item.uuid 273d5800-add1-45bb-8a11-ecd6d8c1503e
> dev_item.fsid 67ac5740-1ced-4d59-8999-03bb3195ec49 [match]
> dev_item.type 0
> dev_item.total_bytes 2147483648
> dev_item.bytes_used 667680768
> dev_item.io_align 4096
> dev_item.io_width 4096
> dev_item.sector_size 4096
> dev_item.devid 1
> dev_item.dev_group 0
> dev_item.seek_speed 0
> dev_item.bandwidth 0
> dev_item.generation 0
Does anyone have an idea why I can't mount it anymore?
Regards,
Tobias
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: cannot mount read-write because of unsupported optional features (2)
2016-11-01 4:46 cannot mount read-write because of unsupported optional features (2) Tobias Holst
@ 2016-11-01 5:24 ` Qu Wenruo
2016-11-01 15:03 ` Tobias Holst
0 siblings, 1 reply; 4+ messages in thread
From: Qu Wenruo @ 2016-11-01 5:24 UTC (permalink / raw)
To: Tobias Holst, linux-btrfs@vger.kernel.org
At 11/01/2016 12:46 PM, Tobias Holst wrote:
> Hi
>
> I can't mount my boot partition anymore. When I try it by entering
> "mount /dev/sdi1 /mnt/boot/" I get:
>> mount: wrong fs type, bad option, bad superblock on /dev/sdi1,
>> missing codepage or helper program, or other error
>>
>> In some cases useful info is found in syslog - try
>> dmesg | tail or so.
>
> "dmesg | tail" gives me:
>> BTRFS info (device sdi1): using free space tree
>> BTRFS info (device sdi1): has skinny extents
>> BTRFS error (device sdi1): cannot mount read-write because of unsupported optional features (2)
>> BTRFS: open_ctree failed
>
> I am using an Ubuntu 16.10 Live CD with Kernel 4.8 and btrfs-progs v4.8.2.
>
> "btrfs inspect-internal dump-super /dev/sdi1" gives me the following:
>> superblock: bytenr=65536, device=/dev/sdi1
>> ---------------------------------------------------------
>> csum_type 0 (crc32c)
>> csum_size 4
>> csum 0x0f346b08 [match]
>> bytenr 65536
>> flags 0x1
>> ( WRITTEN )
>> magic _BHRfS_M [match]
>> fsid 67ac5740-1ced-4d59-8999-03bb3195ec49
>> label t-hyper-boot
>> generation 64
>> root 20971520
>> sys_array_size 129
>> chunk_root_generation 43
>> root_level 1
>> chunk_root 12587008
>> chunk_root_level 0
>> log_root 0
>> log_root_transid 0
>> log_root_level 0
>> total_bytes 2147483648
>> bytes_used 102813696
>> sectorsize 4096
>> nodesize 4096
>> leafsize 4096
>> stripesize 4096
>> root_dir 6
>> num_devices 1
>> compat_flags 0x0
>> compat_ro_flags 0x3
compat_ro_flags 0x3 is FREE_SPACE_TREE and FREE_SPACE_TREE_VALID.
FREE_SPACE_TREE_VALID is introduced later to fix a endian bug in free
space tree.
And that seems to be cause.
Thanks,
Qu
>> incompat_flags 0x34d
>> ( MIXED_BACKREF |
>> MIXED_GROUPS |
>> COMPRESS_LZO |
>> EXTENDED_IREF |
>> SKINNY_METADATA |
>> NO_HOLES )
>> cache_generation 53
>> uuid_tree_generation 64
>> dev_item.uuid 273d5800-add1-45bb-8a11-ecd6d8c1503e
>> dev_item.fsid 67ac5740-1ced-4d59-8999-03bb3195ec49 [match]
>> dev_item.type 0
>> dev_item.total_bytes 2147483648
>> dev_item.bytes_used 667680768
>> dev_item.io_align 4096
>> dev_item.io_width 4096
>> dev_item.sector_size 4096
>> dev_item.devid 1
>> dev_item.dev_group 0
>> dev_item.seek_speed 0
>> dev_item.bandwidth 0
>> dev_item.generation 0
>
> Does anyone have an idea why I can't mount it anymore?
>
> Regards,
> Tobias
> --
> 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
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: cannot mount read-write because of unsupported optional features (2)
2016-11-01 5:24 ` Qu Wenruo
@ 2016-11-01 15:03 ` Tobias Holst
2016-11-01 15:20 ` Omar Sandoval
0 siblings, 1 reply; 4+ messages in thread
From: Tobias Holst @ 2016-11-01 15:03 UTC (permalink / raw)
To: Qu Wenruo; +Cc: linux-btrfs@vger.kernel.org
Ah thanks! Looks like I missed this bug on the list...
But as I understand it, it should be mountable with btrfs-progs
>=4.7.3 or when mounting it with "-o clear_cache,nospace_cache". But
both doesn't work. Is it only mountable with kernel >=4.9 anymore?
That would be interesting since I never ran a kernel newer than 4.8...
Regards,
Tobias
2016-11-01 6:24 GMT+01:00 Qu Wenruo <quwenruo@cn.fujitsu.com>:
>
>
> At 11/01/2016 12:46 PM, Tobias Holst wrote:
>>
>> Hi
>>
>> I can't mount my boot partition anymore. When I try it by entering
>> "mount /dev/sdi1 /mnt/boot/" I get:
>>>
>>> mount: wrong fs type, bad option, bad superblock on /dev/sdi1,
>>> missing codepage or helper program, or other error
>>>
>>> In some cases useful info is found in syslog - try
>>> dmesg | tail or so.
>>
>>
>> "dmesg | tail" gives me:
>>>
>>> BTRFS info (device sdi1): using free space tree
>>> BTRFS info (device sdi1): has skinny extents
>>> BTRFS error (device sdi1): cannot mount read-write because of unsupported
>>> optional features (2)
>>> BTRFS: open_ctree failed
>>
>>
>> I am using an Ubuntu 16.10 Live CD with Kernel 4.8 and btrfs-progs v4.8.2.
>>
>> "btrfs inspect-internal dump-super /dev/sdi1" gives me the following:
>>>
>>> superblock: bytenr=65536, device=/dev/sdi1
>>> ---------------------------------------------------------
>>> csum_type 0 (crc32c)
>>> csum_size 4
>>> csum 0x0f346b08 [match]
>>> bytenr 65536
>>> flags 0x1
>>> ( WRITTEN )
>>> magic _BHRfS_M [match]
>>> fsid 67ac5740-1ced-4d59-8999-03bb3195ec49
>>> label t-hyper-boot
>>> generation 64
>>> root 20971520
>>> sys_array_size 129
>>> chunk_root_generation 43
>>> root_level 1
>>> chunk_root 12587008
>>> chunk_root_level 0
>>> log_root 0
>>> log_root_transid 0
>>> log_root_level 0
>>> total_bytes 2147483648
>>> bytes_used 102813696
>>> sectorsize 4096
>>> nodesize 4096
>>> leafsize 4096
>>> stripesize 4096
>>> root_dir 6
>>> num_devices 1
>>> compat_flags 0x0
>>> compat_ro_flags 0x3
>
> compat_ro_flags 0x3 is FREE_SPACE_TREE and FREE_SPACE_TREE_VALID.
>
> FREE_SPACE_TREE_VALID is introduced later to fix a endian bug in free space
> tree.
>
> And that seems to be cause.
>
> Thanks,
> Qu
>
>>> incompat_flags 0x34d
>>> ( MIXED_BACKREF |
>>> MIXED_GROUPS |
>>> COMPRESS_LZO |
>>> EXTENDED_IREF |
>>> SKINNY_METADATA |
>>> NO_HOLES )
>>> cache_generation 53
>>> uuid_tree_generation 64
>>> dev_item.uuid 273d5800-add1-45bb-8a11-ecd6d8c1503e
>>> dev_item.fsid 67ac5740-1ced-4d59-8999-03bb3195ec49 [match]
>>> dev_item.type 0
>>> dev_item.total_bytes 2147483648
>>> dev_item.bytes_used 667680768
>>> dev_item.io_align 4096
>>> dev_item.io_width 4096
>>> dev_item.sector_size 4096
>>> dev_item.devid 1
>>> dev_item.dev_group 0
>>> dev_item.seek_speed 0
>>> dev_item.bandwidth 0
>>> dev_item.generation 0
>>
>>
>> Does anyone have an idea why I can't mount it anymore?
>>
>> Regards,
>> Tobias
>> --
>> 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
>>
>>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: cannot mount read-write because of unsupported optional features (2)
2016-11-01 15:03 ` Tobias Holst
@ 2016-11-01 15:20 ` Omar Sandoval
0 siblings, 0 replies; 4+ messages in thread
From: Omar Sandoval @ 2016-11-01 15:20 UTC (permalink / raw)
To: Tobias Holst; +Cc: Qu Wenruo, linux-btrfs@vger.kernel.org
On Tue, Nov 01, 2016 at 04:03:38PM +0100, Tobias Holst wrote:
> Ah thanks! Looks like I missed this bug on the list...
>
> But as I understand it, it should be mountable with btrfs-progs
> >=4.7.3 or when mounting it with "-o clear_cache,nospace_cache". But
> both doesn't work. Is it only mountable with kernel >=4.9 anymore?
> That would be interesting since I never ran a kernel newer than 4.8...
>
> Regards,
> Tobias
Hi, Tobias,
The fix was backported to v4.7 and v4.8 stable, so it's not just v4.9.
The btrfs-progs version doesn't matter for mounting. If you use a stable
kernel newer than v4.7.10 or v4.8.4, you will be able to mount it. If
you really need to use it with an older kernel, you can clear the free
space tree with -o clear_cache,nospace_cache from the newer kernel.
Sorry for the trouble, we really had to add this incompatability bit
even for x86 because of a btrfs-progs bug that could potentially corrupt
the free space tree.
--
Omar
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-11-01 15:20 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-01 4:46 cannot mount read-write because of unsupported optional features (2) Tobias Holst
2016-11-01 5:24 ` Qu Wenruo
2016-11-01 15:03 ` Tobias Holst
2016-11-01 15:20 ` Omar Sandoval
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).