Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

restarting udisks seems to unexpectedly mount and then unmount (a previously unmounted) btrfs filesystem #1145

Closed
calestyo opened this issue Jul 14, 2023 · 2 comments · Fixed by #1146
Closed

restarting udisks seems to unexpectedly mount and then unmount (a previously unmounted) btrfs filesystem #1145

calestyo opened this issue Jul 14, 2023 · 2 comments · Fixed by #1146

Comments

@calestyo
Copy link

Hey.

This is forwarded from the corresponding Debian bug.

Every time when restarting udisks2.service, e.g. after it was upgraded to a new version, it seems to unexpectedly mount a btrfs filesystem (which is regularly not mounted on my system and marked as noauto in /etc/fstab) and then automatically unmount it again.

Kernel shows:

Jul 14 05:26:00 heisenberg kernel: BTRFS: device label system-meta devid 1 transid 16 /dev/nvme0n1p3 scanned by udisksd (505610)
Jul 14 05:26:00 heisenberg kernel: BTRFS info (device nvme0n1p3): using crc32c (crc32c-intel) checksum algorithm
Jul 14 05:26:00 heisenberg kernel: BTRFS info (device nvme0n1p3): using free space tree
Jul 14 05:26:00 heisenberg kernel: BTRFS info (device nvme0n1p3): enabling ssd optimizations
Jul 14 05:26:00 heisenberg kernel: BTRFS info (device nvme0n1p3): auto enabling async discard

which are just the messages that also happen when mounting it manually.

As described in the Debian bug, I've run udisksd with --debug which was ought to show me any mounts it does, but it didn't:

Jul 14 05:25:59 heisenberg udisksd[505215]: udisks daemon version 2.10.0 exiting
Jul 14 05:25:59 heisenberg udisksd[505610]: udisks daemon version 2.10.0 starting
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop6' information: Failed to get status of the device loop6: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop0' information: Failed to get status of the device loop0: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop7' information: Failed to get status of the device loop7: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop1' information: Failed to get status of the device loop1: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop2' information: Failed to get status of the device loop2: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop3' information: Failed to get status of the device loop3: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop4' information: Failed to get status of the device loop4: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Error getting 'loop5' information: Failed to get status of the device loop5: No such device or address (g-bd-loop-error-quark, 1)
Jul 14 05:26:00 heisenberg udisksd[505610]: Acquired the name org.freedesktop.UDisks2 on the system message bus

Yet it repeatedly still happens right when restarting its unit.

For a moment when writing this, I thought the issue was gone, because a restart seemed to not cause it again.

However, I only noticed that I had still manually mounted the fs to /mnt/ from my tests last night.

Once I've unmounted the fs, every time I restart the service, it seems to mount it (and then unmount it again immediately.)

I just mention this, as it shows that this issue happens only with unmounted filesystems.

I first noticed this after upgrading to 2.10.0, but I cannot rule out for sure, that it didn't happen in earlier versions, too, though I'd rather say not.

In any case, it shouldn't do this.

Especially since btrfs, like most filesystems is not truly read-only, even if it was mounted as read-only (which I didn't check, whether udisks mounts it that way).

So when doing forensics or rescue operations, such a short time mount may already cause damage.

Any ideas?

Thanks,
Chris.
This was referenced Jul 14, 2023
Closed
Merged
@calestyo
Copy link
Author

btw: I think I've just noticed that it not just mounts the filesystems completely unwarranted, but does so even read-write....

I mean what the...?!?

I manually mount the fs ro via mount (and then unmount it again):

Jul 17 03:06:55 heisenberg kernel: BTRFS: device label data-b-1 devid 1 transid 7187 /dev/mapper/data-b-1 scanned by mount (1084181)
Jul 17 03:06:55 heisenberg kernel: BTRFS info (device dm-1): using crc32c (crc32c-intel) checksum algorithm
Jul 17 03:06:55 heisenberg kernel: BTRFS info (device dm-1): using free space tree

transid is 7187.

I restart udisks2.service:

Jul 17 03:09:06 heisenberg kernel: BTRFS: device label data-b-1 devid 1 transid 7187 /dev/mapper/data-b-1 scanned by udisksd (1084291)
Jul 17 03:09:06 heisenberg kernel: BTRFS info (device dm-1): using crc32c (crc32c-intel) checksum algorithm
Jul 17 03:09:06 heisenberg kernel: BTRFS info (device dm-1): using free space tree

so was still at 7187.

When I now mount it again:

Jul 17 03:10:16 heisenberg kernel: BTRFS: device label data-b-1 devid 1 transid 7188 /dev/mapper/data-b-1 scanned by mount (1084386)
Jul 17 03:10:16 heisenberg kernel: BTRFS info (device dm-1): using crc32c (crc32c-intel) checksum algorithm
Jul 17 03:10:16 heisenberg kernel: BTRFS info (device dm-1): using free space tree

Now it's 7188.

Seriously, there is absolutely no justification for udisks to ever automatically mount any filesystem unless by manually told so by the user/admin … never ever.
Not just btrfs - any fs!

Consider:

  • a user is doing forensics or has a damaged fs, where btrfs, ext and others will change the fs in many cases even if mounted read-only
  • a user has some removable device and unplugs it while udisks thinks it's fun to mount a fs on it
  • and, even a bonus security issue, a fs contains sensitive data an should not be mounted unless precautions are taken (e.g. all other users locked out or so)... and again, udisks mounts it and even if it's just short may leak data... or an attacker simply opens something in it and unmounting fails.

@tbzatek
Copy link
Member

tbzatek commented Jul 18, 2023

This is basically issue #1139, closing as duplicate.

The loop device warnings are essentially harmless, silenced in #1148.

@tbzatek tbzatek closed this as completed Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Limit getting filesystem size only to Ext and XFS vojtechtrefny/storaged
2 participants
@calestyo @tbzatek