Hirsute - dmesg # attach [ 264.065866] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=5 [ 264.065906] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0 [ 264.099347] virtio_blk virtio5: [vdc] 385 512-byte logical blocks (197 kB/193 KiB) # detach [ 289.702243] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=5 [ 289.702267] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0
Groovy - dmesg # attach [ 719.712747] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=5 [ 719.712758] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0 [ 719.745538] virtio_blk virtio5: [vdc] 385 512-byte logical blocks (197 kB/193 KiB) [ 719.745542] vdc: detected capacity change from 0 to 197120 # detach [ 780.425222] crw_info : CRW reports slct=0, oflw=0, chn=1, rsc=3, anc=0, erc=4, rsid=5 [ 780.425233] crw_info : CRW reports slct=0, oflw=0, chn=0, rsc=3, anc=0, erc=4, rsid=0 There is a difference in hirsute missing the capacity change. The newer kernel might immediately do that instead of detecting as zero and then bumping it up. The sizes reported in the Hirsute guest are correct (e.g. 20M for a 20M zfs case). So this might be a red herring unless the missing message makes you very suspicious -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925211 Title: Hot-unplug of disks leaves broken block devices around in Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
