Created attachment 864776 [details] log of os-prober Description of problem: Updated my system, then ran: grub2-mkconfig -o /boot/grub2/grub.cfg It generated 2 errors telling that the ressource was busy for a rmdir command. Version-Release number of selected component (if applicable): os-prober-1.58-4.fc20.x86_64 grub2-2.00-25.fc20.x86_64 grub2-tools-2.00-25.fc20.x86_64 How reproducible: Cannot reproduce it at this time Actual results: Sorry, my system is in french # grub2-mkconfig -o /boot/grub2/grub.cfg Création de grub.cfg… Image Linux trouvée : /boot/vmlinuz-3.13.3-201.fc20.x86_64 Image mémoire initiale trouvée : /boot/initramfs-3.13.3-201.fc20.x86_64.img Image Linux trouvée : /boot/vmlinuz-3.13.3-200.fc20.x86_64 Image mémoire initiale trouvée : /boot/initramfs-3.13.3-200.fc20.x86_64.img Image Linux trouvée : /boot/vmlinuz-3.12.10-300.fc20.x86_64 Image mémoire initiale trouvée : /boot/initramfs-3.12.10-300.fc20.x86_64.img Image Linux trouvée : /boot/vmlinuz-0-rescue-6ef65b7784ff4fa0a209ee9445902e13 Image mémoire initiale trouvée : /boot/initramfs-0-rescue-6ef65b7784ff4fa0a209ee9445902e13.img umount: /var/lib/os-prober/mount : cible occupée (Dans certains cas, des renseignements sur les processus utilisant le périphérique sont accessibles avec lsof(8) ou fuser(1).) rmdir: échec de suppression de « /var/lib/os-prober/mount »: Périphérique ou ressource occupé fait The mount command returned this: /dev/sdb1 on /var/lib/os-prober/mount type btrfs (rw,relatime,seclabel,space_cache) Additional info: Attached the log I got from /var/log/messages Not sure why I get my username in front of os-prober debug I was able to umount /var/lib/os-prober/mount sucessfuly, then I couldn't reproduce it.
In the log, at the end, there is this: user: 50mounted-tests: warning: cannot mount btrfs volume b4751035-e033-4770-b0b5-b94fabeb57e1, exiting user: os-prober: debug: running /usr/libexec/os-probes/50mounted-tests on /dev/block/8 user: 50mounted-tests: debug: /dev/block/8 type not recognised; skipping I am not sure I understand why it reports it couldn't mount /dev/sdb1 (b4751035-e033-4770-b0b5-b94fabeb57e1), as it was mounted when I looked. I don't have a /dev/block/8, and not sure where it has found it: # ls -lZ /dev/block lrwxrwxrwx. root root system_u:object_r:device_t:s0 11:0 -> ../sr0 lrwxrwxrwx. root root system_u:object_r:device_t:s0 253:0 -> ../dm-0 lrwxrwxrwx. root root system_u:object_r:device_t:s0 8:0 -> ../sda lrwxrwxrwx. root root system_u:object_r:device_t:s0 8:1 -> ../sda1 lrwxrwxrwx. root root system_u:object_r:device_t:s0 8:16 -> ../sdb lrwxrwxrwx. root root system_u:object_r:device_t:s0 8:17 -> ../sdb1 lrwxrwxrwx. root root system_u:object_r:device_t:s0 8:2 -> ../sda2 lrwxrwxrwx. root root system_u:object_r:device_t:s0 8:3 -> ../sda3 lrwxrwxrwx. root root system_u:object_r:device_t:s0 8:4 -> ../sda4 lrwxrwxrwx. root root system_u:object_r:device_t:s0 8:5 -> ../sda5
Correction. At this time I can reproduce it all the time, if I don't have /dev/sdb1 already mounted by systemd. If I have it mounted by systemd, I don't get the errors. /etc/fstab: /dev/sdb1 /mnt/backup btrfs defaults,noexec,nosuid,noauto,x-systemd.automount,x-systemd.device-timeout=10 0 0 If I umount /dev/sdb1, and run the grub2-mkconfig command, I get all the time these errors at the end of the command: umount: /var/lib/os-prober/mount: target is busy (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1).) rmdir: failed to remove '/var/lib/os-prober/mount': Device or resource busy and mount shows after that: /dev/sdb1 on /var/lib/os-prober/mount type btrfs (rw,relatime,seclabel,space_cache) (still no /dev/block/8 though, maybe a parse error because of the ':' ?)
It is maybe the same bug than #903906 I am not on kde, I am on Mate.
Sorry for the late reply, I'll try to look into this ASAP. The umount problem is the same as 903906, but I should check for /dev/block/8
I don't seem to be able to trigger this bug anymore. Will check longer to see if I can reproduce it again, or will post here if it reappears.
Thank you for the update. I checked the /dev/block/8 problem and it is harmless and related to our btrfs support. I mark this as duplicate of 903906 and will try to fix it by retrying umount a few times if it failed the first time. *** This bug has been marked as a duplicate of bug 903906 ***