Heitor, I thought I was crossing some etiquette boundary and being ignored (snubbed!) and was hesitant to comment further!!! Regardless, some caution as you are testing the memory of a 70 year old who is taking bad (perscription) drugs that **** up my memory (yes I am still sick after 5 years - it sucks). That said I believe grub-mount has access to the full running linux system of filesystems, but grub-probe (intentionally) doesn't.
In the two cases I discovered thin-lvms and thick lvm snapshots, both were mountable by grub-mount and grub-probe failed (i.e. returned an error code). As I wrote at the beginning of the bug report, when I fixed the bug as you have I discovered that the thin-lvm was ignored, but the thick snapshot was added to the cfg file, but as the base by one of the "mounted" probes". This results in the really bad situation that all will work until the user tries to update grub or the cfg file in the thick snapshot as it will have no effect and I expect the user will have a really hard time figuring it out. My latest suggestion may not be perfect, but it makes things better (never leaves a file system mounted - even if it is because of user error) and never makes it worse. Perhaps juliank can provide better insight on grub-mount vs grub-probe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1987679 Title: os-prober leaves filesystems (lvm-thin, lvm snap) mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1987679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
