#3469 PR open: Describe enforced umount problem in umount_mountpoint_retry_lazy function¶

Labels: documentation

jsmeix opened issue at 2025-05-06 11:04:¶

• Type: Enhancement

• Impact: Low

• Description of the changes in this pull request:

In lib/global-functions.sh
for the umount_mountpoint_retry_lazy function
add a comment that shows an example
why enforced umount raises its own specific troubles:
Enforced umount may corrupt data
when it disrupts a writing process, e.g. see
https://stackoverflow.com/questions/7878707/how-to-unmount-a-busy-device
which reads (excerpts)

umount -l /PATH/OF/BUSY-DEVICE
umount -f /PATH/OF/BUSY-NFS
...
NOTE/CAUTION
These commands can disrupt a running process,
cause data loss OR corrupt open files.
Programs accessing target DEVICE/NFS files
may throw errors OR could not work properly
after force unmount.

gdha commented at 2025-05-06 12:03:¶

@jsmeix Thank you Johannes for the updated comments - makes it much clearer. However, wait with the merge until I'm done with my umount function.

---

[Export of Github issue for rear/rear.]