File util-linux-umount-losetup-lazy-destruction-gene... of Package python3-libmount.34962

Overview Repositories Revisions Requests Users Attributes Meta

File util-linux-umount-losetup-lazy-destruction-generated.patch of Package python3-libmount.34962

Index: util-linux-2.37.4/sys-utils/umount.8
===================================================================
--- util-linux-2.37.4.orig/sys-utils/umount.8
+++ util-linux-2.37.4/sys-utils/umount.8
@@ -156,6 +156,8 @@ Since version 2.35 \fBumount\fP command
 The \fBumount\fP command will automatically detach loop device previously initialized by \fBmount\fP(8) command independently of \fI/etc/mtab\fP.
 .sp
 In this case the device is initialized with "autoclear" flag (see \fBlosetup\fP(8) output for more details), otherwise it\(cqs necessary to use the option \fB\-\-detach\-loop\fP or call \fBlosetup \-d <device>\fP. The autoclear feature is supported since Linux 2.6.25.
+.sp
+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 \fBudevadm settle\fP after \fBumount\fP.
 .SH "EXTERNAL HELPERS"
 .sp
 The syntax of external unmount helpers is:
Index: util-linux-2.37.4/sys-utils/losetup.8
===================================================================
--- util-linux-2.37.4.orig/sys-utils/losetup.8
+++ util-linux-2.37.4/sys-utils/losetup.8
@@ -74,7 +74,7 @@ Show the status of all loop devices. Not
 .sp
 \fB\-d\fP, \fB\-\-detach\fP \fIloopdev\fP...
 .RS 4
-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 \fBEBUSY\fP 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 \fBEBUSY\fP 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 \fBudevadm settle\fP after \fBlosetup\fP.
 .RE
 .sp
 \fB\-D\fP, \fB\-\-detach\-all\fP

Places

File util-linux-umount-losetup-lazy-destruction-generated.patch of Package python3-libmount.34962

Places