GNU GRUB - Bugs: bug #56521, os-prober creates a dm by dmsetup...
You are not allowed to post comments on this tracker with your current authentication level.
bug #56521: os-prober creates a dm by dmsetup but can not remove it.
Submitter: | 王烁 <shuo> | ||
Submitted: | Wed 19 Jun 2019 03:33:40 AM UTC | ||
Category: | Disk & Partition | Severity: | Major |
Priority: | 5 - Normal | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Wangshuo |
Open/Closed: | Open | Release: | 2.02 |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
Powered by Savane 3.13-d3ae.
Corresponding source code
There are two os located in "/" and "/target" respectively. After we type grub2-mkconfig, several unpredictable dm devices are created (The prefix of these dm devices is same: osprober-linux).
Finally, we find grub2-mkconfig call os-prober and then the latter will call a function (do_dmsetup, it create dm devices by dmsetup create) to create dm devices. The dm devices will be removed by another function (do_unmount, it remove dm devices by dmsetup remove)after many test normally, however it may spend many time to create a dm device and when do_unmount is called, the new dm device still can not be find until do_unmount function ends. Therefore
this dm device will be kept.
If we add "sleep 2" after do_dmsetup, the issue will be resolved, however it is an unreliable way obviously.
Is there any more reliable way?