diff options
| author | Laurent Bercot <ska-skaware@skarnet.org> | 2026-05-23 12:30:44 +0000 |
|---|---|---|
| committer | Laurent Bercot <ska-skaware@skarnet.org> | 2026-05-23 12:30:44 +0000 |
| commit | 7329cd1b23ba51c9ea8f526dbd491b8cd9d5b822 (patch) | |
| tree | 6f4a757704252308d42662f1a066fd5490a213e5 /doc/s6-linux-init-umountall.html | |
| parent | 94830d74874b9192faeeebda281029250dd825e7 (diff) | |
| download | s6-linux-init-7329cd1b23ba51c9ea8f526dbd491b8cd9d5b822.tar.gz | |
Prepare for 1.2.0.2; attempt ro remount if umount fails
Diffstat (limited to 'doc/s6-linux-init-umountall.html')
| -rw-r--r-- | doc/s6-linux-init-umountall.html | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/s6-linux-init-umountall.html b/doc/s6-linux-init-umountall.html index 152cfb5..b922a44 100644 --- a/doc/s6-linux-init-umountall.html +++ b/doc/s6-linux-init-umountall.html @@ -57,7 +57,9 @@ when attempting to unmount the filesystems listed in <tt>/proc/mounts</tt>. in "stage 4", i.e. after a SIGKILL has been sent to all the processes on the system, and right before the system reboots (or halts, or is powered off). By that point, there is no possible process that could prevent real file systems from being unmounted. </li> - <li> It is likely that some filesystems will still fail to unmount, typically + <li> If a filesystem cannot be unmounted because it is busy, <tt>s6-linux-init-umountall</tt> +attempts to remount it read-only instead. </li> + <li> It is likely that some filesystems will still fail, typically cgroups or tmpfses. That's okay: those are pseudo-filesystems, and will not cause data loss or a fsck if the system shuts down while they are still mounted. </li> <li> Distributions usually provide a <tt>umount</tt> command with a <tt>-a</tt> option |