On Tue, Oct 02, 2018 at 03:01:13PM -0000, Joseph Salisbury wrote: > Bionic already has commit 639812a1ed9b since it was added to mainline as > of v4.14-rc6: > > 639812a1ed9b nbd: don't set the device size until we're connected > > Can you confirm Bionic has this bug after applying all the latest > updates? If it does, we can perform a "Reverse" bisect, since you > confirm this bug is fixed in 4.19-rc5.
Just tested again against kernel 4.15.0-36-generic #39-Ubuntu SMP (linux-image-generic: Installed: 4.15.0.36.38) but a "rbd resize" on the ceph cluster does *not* propagate to the rbd-nbd session. Bug is still present. Gr. Stefan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794766 Title: nbd device size not updated correctly Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: nbd does not handle a disk resize correctly. This has been fixed upstream: https://github.com/torvalds/linux/commit/639812a1ed9bf49ae2c026086fbf975339cd1eef On Ubuntu Bionic with a "4.15.0-34-generic #37-Ubuntu" kernel a resize of a (Ceph) rbd image does not propagate to a "rbd-nbd" mapped disk, until it's unmapped / remapped. See https://tracker.ceph.com/issues/23137. Other "nbd" mapped disks might suffer from the same behaviour (not tested). Ubuntu mainline kernel (4.19-rc5) works correct with regards to this rbd resize rbd-nbd mapped image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794766/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
