Skip to contentSkip to conversation

umount, losetup: Document loop destroy behavior

PATCH Applied Stanislav Brabec 2 participants 2 messages Jun 19, 2024 – Jun 20, 2024 Util-Linux package

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 umount, losetup: Document loop destroy behavior

The loop device detach runs asynchronously in the background. It can cause unexpected errors. Document the possible existence of the loop device after exit of losetup -d or umount and need of "udevadm settle".

---
 sys-utils/losetup.8.adoc | 2 +-
 sys-utils/umount.8.adoc  | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)
sys-utils/losetup.8.adoc +1 -1
index 9ea9451ce..e22e650b8 100644
@@ -54,7 +54,7 @@ The _size_ and _offset_ arguments may be followed by the multiplicative suffixes
 Show the status of all loop devices. Note that not all information is accessible for non-root users. See also *--list*. The old output format (as printed without *--list*) is deprecated.
 
 *-d*, *--detach* _loopdev_...::
-Detach the file or device associated with the specified loop device(s). Note that since Linux v3.7 kernel uses "lazy device destruction". The detach operation does not return *EBUSY* error anymore if device is actively used by system, but it is marked by autoclear flag and destroyed later.
+Detach the file or device associated with the specified loop device(s). Note that since Linux v3.7 kernel uses "lazy device destruction". The detach operation does not return *EBUSY* error anymore if device is actively used by system, but it is marked by autoclear flag and destroyed later. Even if the device is not used, the loop device can be destroyed later. If you need to wait for a complete removal of the loop device, call *udevadm settle* after *losetup*.
 
 *-D*, *--detach-all*::
 Detach all associated loop devices.
sys-utils/umount.8.adoc +2 -0
index f9b96e1ff..b9a3ff963 100644
@@ -127,6 +127,8 @@ The *umount* command will automatically detach loop device previously initialize
 
 In this case the device is initialized with "autoclear" flag (see *losetup*(8) output for more details), otherwise it's necessary to use the option *--detach-loop* or call *losetup -d* _device_. The autoclear feature is supported since Linux 2.6.25.
 
+Note that since Linux v3.7 kernel uses "lazy device destruction". The system just marks the loop device by autoclear flag and destroys it later. If you need to wait for a complete removal of the loop device, call *udevadm settle* after *umount*.
+
 == EXIT STATUS
 
 *umount* has the following exit status values (the bits can be ORed):
Signature · 1 line
2.45.0
maintainer Applied
#1 lore raw
Quoted 3 lines · Stanislav Brabec
 sys-utils/losetup.8.adoc | 2 +-
 sys-utils/umount.8.adoc  | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

Applied, thanks!

Karel

Signature · 2 lines
 Karel Zak  <[email protected]>
 http://karelzak.blogspot.com