> I rebootet with HWE K4.11 > > and took a pic of the error message (see attachment). > > It seems btrfs still sees the removed NVME. > There is a mismatch from super_num_devices (3) to num_devices (2) > with indicates something strage is going on here, imho. > > Then i returned and booted K4.4, which boots fine. > > root@vHost1:~# btrfs dev stat / > [/dev/nvme0n1p1].write_io_errs 0 > [/dev/nvme0n1p1].read_io_errs 0 > [/dev/nvme0n1p1].flush_io_errs 0 > [/dev/nvme0n1p1].corruption_errs 0 > [/dev/nvme0n1p1].generation_errs 0 > [/dev/sda1].write_io_errs 0 > [/dev/sda1].read_io_errs 0 > [/dev/sda1].flush_io_errs 0 > [/dev/sda1].corruption_errs 0 > [/dev/sda1].generation_errs 0 > > Btw i edited the subject to match the correct error. > > > Sash Thats very odd, if super_num_devices in superblocks don't match real number of devices then 4.4 kernel shouldn't mount the filesystem too. We probably need help from one of btrfs developers since I'm not one, I'm just btrfs user. Can you provide outpus of: btrfs inspect-internal dump-super -f /dev/sda1 btrfs inspect-internal dump-super -f /dev/nvme0n1p1 Depending on version of btrfs-progs you may need to use btrfs-dump-super instead of "btrfs inspect-internal dump-super" >3rd i saw https://patchwork.kernel.org/patch/9419189/ from Roman. Did >he receive any comments on his patch? This one could help on this >problem, too. Don't know about this patch from Roman per se, but there is a patchset[1] which is aimed to be merged in 4.14 merge window AFAIK. [1] https://www.spinics.net/lists/linux-btrfs/msg66891.html -- 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
