Bug 1919085

Summary: mount: /var/lib/os-prober/mount: mount(2) system call failed: No such file or directory
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: os-proberAssignee: Hedayat Vatankhah <hedayatv>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: agk, hedayatv
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-11 20:24:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
strace files for os-prober none

Description Chris Murphy 2021-01-22 05:07:57 UTC
Created attachment 1749619 [details]
strace files for os-prober

Description of problem:

When running 'os-prober' or 'grub2-mkconfig' I get an error message from os-prober. It appears to be related to the existence of /srv being a subvolume...


Version-Release number of selected component (if applicable):
os-prober-1.77-6.fc33.x86_64

How reproducible:
Always on this one machine, another Fedora 33 system (but without Windows) doesn't have this problem.

Steps to Reproduce:
1. Run grub2-mkconfig or os-prober
2.
3.

Actual results:

# os-prober 
/dev/nvme0n1p2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
mount: /var/lib/os-prober/mount: mount(2) system call failed: No such file or directory.
[root@flap ~]# 



Expected results:

No error.


Additional info:


Curiously, while the error shows up with 'strace' without options, it's not found in any of the many files when I use 'strace -o osprober.txt -ff' but it did give me a clue. It looks like it's getting tripped up on /srv being a Btrfs subvolume. I have no idea why it's a Btrfs subvolume, that's not something I recall ever doing, but anyway, when I remove that subvolume and replace with a directory - the error no longer happens.

Comment 1 Chris Murphy 2021-01-22 05:45:11 UTC
OK no that's not correct. It started happening again on the original computer, and now also happens on the 2nd computer. I have no idea why.

Comment 2 Hedayat Vatankhah 2021-04-11 19:54:20 UTC
Thanks for the report, and sorry for the late answer.

Would you please also attach os-prober logs? It logs to syslog, which appears in journalctl output. You might filter its log afterwards (for which I don't know the exact command right now!), our just run `journalctl -f > os-prober.log` before running os-prober and terminate it afterwards. Then attach the log here.

Comment 3 Chris Murphy 2021-04-11 20:24:17 UTC
I can't reproduce it. One of the systems is still F33, and has os-prober-1.77-6.fc33.x86_64 but the problem doesn't happen anymore. Mysterious. I'll reopen if it reoccurs.

Comment 4 Hedayat Vatankhah 2021-04-12 10:19:23 UTC
OK, thanks. Sorry again for late reply.