Searched refs:unmounted (Results 1 – 24 of 24) sorted by relevance
/linux-6.12.1/fs/orangefs/ ! |
D | devorangefs-req.c | 86 int unmounted = 1; in mark_all_pending_mounts() local 93 unmounted = 0; in mark_all_pending_mounts() 96 return unmounted; in mark_all_pending_mounts() 525 int unmounted = 0; in orangefs_devreq_release() local 536 unmounted = mark_all_pending_mounts(); in orangefs_devreq_release() 538 (unmounted ? "UNMOUNTED" : "MOUNTED")); in orangefs_devreq_release()
|
/linux-6.12.1/Documentation/filesystems/ ! |
D | automount-support.rst | 61 from the namespace and thrown away (effectively unmounted). 89 mountpoint will not be marked for expiration or unmounted. 92 error will be given and it won't be unmounted.
|
D | sharedsubtree.rst | 275 to the same peer group. Anything mounted or unmounted under 572 sub-mounts within them are unmounted. 583 if 'C1' is unmounted, all the mounts that are most-recently-mounted on 584 'B1' and on the mounts that 'B1' propagates-to are unmounted. 589 So all 'C1', 'C2' and 'C3' should be unmounted. 592 unmounted, but all other mounts are unmounted. However if 'C1' is told 593 to be unmounted and 'C1' has some sub-mounts, the umount operation is 682 unmounted or moved. Bind mounts continue to exist even if the 683 other mount is unmounted or moved.
|
D | afs.rst | 115 Automatically mounted filesystems will be automatically unmounted approximately 116 twenty minutes after they were last used. Alternatively they can be unmounted 121 unmounted, otherwise error EBUSY will be returned.
|
D | autofs.rst | 234 unmounted. So it is generally safest to use the autofs expiry 256 considers if the entire mount-tree can be unmounted or not. For an 258 directory to determine if any of those can be unmounted and cleaned 397 the filesystem could be unmounted. This is only a hint as 412 that can be unmounted or removed. If nothing can be expired,
|
D | inotify.rst | 26 unmounted. Watching a file should not require that it be open.
|
D | ext2.rst | 127 was mounted (and if it was cleanly unmounted), when it was modified, 228 run if the filesystem was not cleanly unmounted, if the maximum mount
|
D | fiemap.rst | 147 unmounted, and then only if the FIEMAP_EXTENT_ENCODED flag is
|
D | fuse.rst | 199 filesystem is still attached (it hasn't been lazy unmounted)
|
D | fscrypt.rst | 898 allow re-adding keys after a filesystem is unmounted and re-mounted,
|
D | path-lookup.rst | 550 unmounted, the ``d_manage()`` function will usually wait for that
|
/linux-6.12.1/Documentation/admin-guide/ ! |
D | initrd.rst | 12 to a directory and can be subsequently unmounted. 262 Now, the initrd can be unmounted and the memory allocated by the RAM 295 modified, then unmounted, and finally, the image is written from 335 unmounted, or, if it is still busy, moved to a directory ``/initrd``, if
|
D | binderfs.rst | 74 binderfs instance is unmounted and all references to it have been dropped.
|
D | ext4.rst | 168 not unmounted cleanly, skipping the journal replay will lead to the 336 file system is unmounted.
|
D | sysrq.rst | 200 ``umount(u)`` can be used to mark filesystems as properly unmounted. From the
|
D | xfs.rst | 154 If the filesystem was not cleanly unmounted, it is likely to
|
/linux-6.12.1/Documentation/ABI/testing/ ! |
D | sysfs-ocfs2 | 63 when all filesystems are unmounted and the cluster stack
|
/linux-6.12.1/Documentation/admin-guide/blockdev/ ! |
D | ramdisk.rst | 89 unused disk partition (such as an unmounted swap partition). For this
|
/linux-6.12.1/Documentation/power/ ! |
D | userland-swsusp.rst | 141 a file on a partition that is unmounted before SNAPSHOT_CREATE_IMAGE and
|
/linux-6.12.1/fs/affs/ ! |
D | Changes | 145 restored when the fs is unmounted. (BH)
|
/linux-6.12.1/fs/ ! |
D | namespace.c | 80 static HLIST_HEAD(unmounted); /* protected by namespace_sem */ 1693 hlist_move_list(&unmounted, &head); in namespace_unlock() 1808 hlist_add_head(&p->mnt_umount, &unmounted); in umount_tree() 1961 hlist_add_head(&mnt->mnt_umount, &unmounted); in __detach_mounts()
|
/linux-6.12.1/Documentation/admin-guide/cgroup-v1/ ! |
D | cgroups.rst | 224 When a cgroup filesystem is unmounted, if there are any 226 will remain active even though unmounted; if there are no
|
/linux-6.12.1/Documentation/cdrom/ ! |
D | cdrom-standard.rst | 717 the tray is opened on the last release, i. e., if a CD-ROM is unmounted,
|
/linux-6.12.1/Documentation/filesystems/xfs/ ! |
D | xfs-online-fsck-design.rst | 123 (``xfs_db``) and can only be used with unmounted filesystems. 131 Like its predecessor, it can only be used with unmounted filesystems. 3063 unmounted cleanly. 3130 | This can happen if the filesystem is unmounted while the underlying |
|