Searched full:mount (Results 1 – 25 of 260) sorted by relevance
1234567891011
| /Documentation/filesystems/ |
| D | sharedsubtree.rst | 10 3) Setting mount states
36 a. shared mount
37 b. slave mount
38 c. private mount
39 d. unbindable mount
42 2a) A shared mount can be replicated to as many mountpoints and all the
47 Let's say /mnt has a mount that is shared::
49 mount --make-shared /mnt
51 Note: mount(8) command now supports the --make-shared flag,
57 # mount --bind /mnt /tmp
[all …]
|
| D | autofs-mount-control.rst | 17 are things such as setting an autofs mount catatonic, setting the
20 mount itself which prevents us being able to use open(2) to obtain a
25 needs to walk back up the mount tree to construct a path, such as
28 from the mount tree.
33 because autofs direct mounts and the implementation of "on demand mount
34 and expire" of nested mount trees have the file system mounted directly
35 on top of the mount trigger directory dentry.
39 a direct mount in disguise) and indirect.
62 operation. So we see a mount of shark:/autofs/export1 on /test/g1, for
65 The way that direct mounts are handled is by making an autofs mount on
[all …]
|
| D | autofs.rst | 46 symbolic links and mount traps. Mount traps are directories with
51 mount traps are created with `mkdir`. The determination of whether a
52 directory should be a mount trap is based on a master map. This master
53 map is consulted by autofs to determine which directories are mount
54 points. Mount points can be *direct*/*indirect*/*offset*.
57 If neither the *direct* or *offset* mount options are given (so the
58 mount is considered to be *indirect*), then the root directory is
59 always a regular directory, otherwise it is a mount trap when it is
62 directory is a mount trap only if the filesystem is mounted *direct*
65 Directories created in the root directory are mount traps only if the
[all …]
|
| D | gfs2-uevents.rst | 7 During the lifetime of a GFS2 mount, a number of uevents are generated.
17 The ADD event occurs at mount time. It will always be the first
18 uevent generated by the newly created filesystem. If the mount
23 and RDONLY=[0|1] that specify the spectator status (a read-only mount
30 The ONLINE uevent is generated after a successful mount or remount. It
40 successful mount of the filesystem by the first node (FIRSTMOUNT=Done).
42 nodes in the cluster to mount the filesystem.
49 for every journal recovered, whether it is during the initial mount
58 uevent for a successful mount or remount.
71 The REMOVE uevent is generated at the end of an unsuccessful mount
[all …]
|
| D | fuse.rst | 18 Non-privileged mount (or user mount):
31 Mount owner:
41 module (fuse.ko), a userspace library (libfuse.*) and a mount utility
55 The filesystem type given to mount(2) can be one of the following:
58 This is the usual way to mount a FUSE filesystem. The first
59 argument of the mount system call may contain an arbitrary string,
64 mount system call is interpreted as the name of the device.
66 Mount options
78 The numeric user id of the mount owner.
81 The numeric group id of the mount owner.
[all …]
|
| D | tmpfs.rst | 17 mount. tmpfs also supports THP.
21 fly using a remount ('mount -o remount ...') of the filesystem. A tmpfs
45 1) There is always a kernel internal mount which you will not see at
49 This mount does not depend on CONFIG_TMPFS. If CONFIG_TMPFS is not
59 Remember to create the directory that you intend to mount tmpfs on
62 This mount is _not_ needed for SYSV shared memory. The internal
63 mount is used for that. (In the 2.3 kernel versions it was
64 necessary to mount the predecessor of tmpfs (shm fs) to use SYSV
67 3) Some people (including me) find it very convenient to mount it
75 tmpfs has three mount options for sizing:
[all …]
|
| D | devpts.rst | 7 Each mount of the devpts filesystem is now distinct such that ptys
8 and their indices allocated in one mount are independent from ptys
21 to bind mount ``/dev/ptx/ptmx`` to ``/dev/ptmx``. If you opt for using
28 kernel.pty.reserve = 1024 - reserved for filesystems mounted from the initial mount namespace
31 Per-instance limit could be set by adding mount option ``max=<count>``.
|
| D | idmappings.rst | 382 - mount's idmapping (``mnt_idmap(vfsmnt)``)
384 Let's see some examples with caller/filesystem idmapping but without mount
386 revisit/reconsider these examples, this time using mount idmappings, to see how
469 userspace id. We could only do this if we were to mount the whole filesystem
606 change in ownership is tied to the lifetime of the filesystem mount, i.e. the
608 filesystem and mount it again in another user namespace. This is usually
625 localized way. The ownership changes are restricted to a specific mount and the
626 ownership changes are tied to the lifetime of the mount. All other users and
631 completely under an idmapped mount to get the same effect. This has the
638 Filesystem types vs idmapped mount types
[all …]
|
| D | ecryptfs.rst | 37 then copy the files back into the new eCryptfs mount to migrate the
41 Mount-wide Passphrase
45 files (i.e., /root/crypt). Then, create the mount point directory
46 (i.e., /mnt/crypt). Now it's time to mount eCryptfs::
48 mount -t ecryptfs /root/crypt /mnt/crypt
65 Then umount /mnt/crypt and mount again per the instructions given
78 mount a directory that has pre-existing files not created by eCryptfs,
|
| D | overlayfs.rst | 35 make the overlay mount more compliant with filesystem scanners and
48 The "xino" feature can be enabled with the "-o xino=on" overlay mount option.
51 the lifetime of the filesystem. The "-o xino=auto" overlay mount option
120 At mount time, the two directories given as mount options "lowerdir" and
123 mount -t overlay overlay -olowerdir=/lower,upperdir=/upper,\
237 Mount options:
299 2) task creating the overlay mount MUST NOT gain additional privileges
325 mount -t overlay overlay -olowerdir=/lower,upperdir=/upper,... /merged
330 mount --bind /upper /merged
342 mount -t overlay overlay -olowerdir=/lower1:/lower2:/lower3 /merged
[all …]
|
| D | virtiofs.rst | 15 guest to mount a directory that has been exported on the host.
33 Mount file system with tag ``myfs`` on ``/mnt``:
37 guest# mount -t virtiofs myfs /mnt
42 Mount options
45 virtiofs supports general VFS mount options, for example, remount,
46 ro, rw, context, etc. It also supports FUSE mount options.
51 The atime-related mount options, for example, noatime, strictatime,
|
| D | incfs.rst | 33 report_uid mount option
41 Optional per mount
44 For each incfs mount, the mount option sysfs_name=[name] creates a /sys/fs
56 Returns total delay time for all files since first mount as a result of the
64 Returns total delay time for all files since first mount as a result of
|
| D | ceph.rst | 93 Mount Syntax
96 The basic mount syntax is::
98 # mount -t ceph user@fsid.fs_name=/[subdir] mnt -o mon_addr=monip1[:port][/monip2[:port]]
102 happens to be down, the mount won't succeed.) The port can be left
106 …# mount -t ceph cephuser@07fe3187-00d9-42a3-814b-72a4d5e7d5be.cephfs=/ /mnt/ceph -o mon_addr=1.2.3…
108 is sufficient. If /sbin/mount.ceph is installed, a hostname can be
110 (as the mount helper will fill it in by reading the ceph configuration
113 # mount -t ceph cephuser@cephfs=/ /mnt/ceph -o mon_addr=mon-addr
117 # mount -t ceph cephuser@cephfs=/ /mnt/ceph -o mon_addr=192.168.1.100/192.168.1.101
119 When using the mount helper, monitor address can be read from ceph
[all …]
|
| D | afs.rst | 88 mount -t afs "%cambridge.redhat.com:root.afs." /afs
89 mount -t afs "#cambridge.redhat.com:root.cell." /afs/cambridge
90 mount -t afs "#root.afs." /afs
91 mount -t afs "#root.cell." /afs/cambridge
100 The name of the cell is optional, and if not given during a mount, then the
110 symbolic links (of the same form as the "device name" passed to mount). kAFS
132 A mount option is available to create a serverless mount that is only usable
133 for dynamic lookup. Creating such a mount can be done by, for example::
135 mount -t afs none /afs -o dyn
137 This creates a mount that just has an empty directory at the root. Attempting
|
| D | zonefs.rst | 71 mount, zonefs uses blkdev_report_zones() to obtain the device zone configuration
72 and populates the mount point with a static file tree solely based on this
86 sub-directory automatically created on mount.
256 with the "errors=xxx" mount option. The table below summarizes the result of
257 zonefs I/O error processing depending on the mount option and on the zone
263 | mount | zone | file file device zone |
285 * The "errors=remount-ro" mount option is the default behavior of zonefs I/O
286 error processing if no errors mount option is specified.
287 * With the "errors=remount-ro" mount option, the change of the file access
298 zone-offline mount options are temporary for zones in a good condition.
[all …]
|
| D | nilfs2.rst | 22 concurrently with its writable mount, and this feature is convenient
27 "mount.nilfs2", "umount.nilfs2", and "nilfs_cleanerd" (so called
47 Mount options
50 NILFS2 supports the following mount options:
65 so a read-only mount option must be specified together.
78 norecovery Disable recovery of the filesystem on mount.
160 # mount -t nilfs2 /dev/block_device /dir
162 This will also invoke the cleaner through the mount helper program
163 (mount.nilfs2).
175 To mount a snapshot::
[all …]
|
| D | ubifs.rst | 71 trees), so the mount time and memory consumption do not linearly depend
83 Mount options
114 The UBI volume to mount is specified using "ubiX_Y" or "ubiX:NAME" syntax,
118 Mount volume 0 on UBI device 0 to /mnt/ubifs::
120 $ mount -t ubifs ubi0_0 /mnt/ubifs
122 Mount "rootfs" volume of UBI device 0 to /mnt/ubifs ("rootfs" is volume
125 $ mount -t ubifs ubi0:rootfs /mnt/ubifs
128 to UBI and mount volume "rootfs":
|
| D | 9p.rst | 41 mount -t 9p 10.10.1.2 /mnt/9
45 mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER
49 mount -t 9p -o trans=virtio <mount_tag> /mnt/9
52 mount points. Each 9P export is seen by the client as a virtio device with an
53 associated "mount_tag" property. Available mount tags can be
59 To mount a 9p FS on a USB Host accessible via the gadget at runtime::
61 mount -t 9p -o trans=usbg,aname=/path/to/fs <device> /mnt/9
63 To mount a 9p FS on a USB Host accessible via the gadget as root filesystem::
119 unix specifying a named pipe mount point
129 uname=name user name to attempt mount as on the remote server. The
[all …]
|
| /Documentation/admin-guide/cifs/ |
| D | usage.rst | 54 If you do not have the utility mount.cifs (in the Samba 4.x source tree and on
55 the CIFS VFS web site) copy it to the same directory in which mount helpers
57 required, mount.cifs is recommended. Most distros include a ``cifs-utils``
62 domain to the proper network user. The mount.cifs mount helper can be
78 the new default. To use old dialects (e.g. to mount Windows XP) use "vers=1.0"
79 on mount (or vers=2.0 for Windows Vista). Note that the CIFS (vers=1.0) is
83 There are additional mount options that may be helpful for SMB3 to get
91 To permit users to mount and unmount over directories they own is possible
92 with the cifs vfs. A way to enable such mounting is to mark the mount.cifs
93 utility as suid (e.g. ``chmod +s /sbin/mount.cifs``). To enable users to
[all …]
|
| D | introduction.rst | 19 Storage vendors, so this network filesystem client can mount to a
36 This filesystem has a mount utility (mount.cifs) and various user space
45 mount.cifs should be installed in the directory with the other mount helpers.
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-rdma.rst | 55 An NFS/RDMA mount point can be obtained by using the mount.nfs command in
59 mount.nfs you are using, type:
63 $ /sbin/mount.nfs -V
73 these to create an NFS/RDMA enabled mount command), the installation
84 After building the nfs-utils package, there will be a mount.nfs binary in
85 the utils/mount directory. This binary can be used to initiate NFS v2, v3,
86 or v4 mounts. To initiate a v4 mount, the binary must be called
87 mount.nfs4. The standard technique is to create a symlink called
88 mount.nfs4 to mount.nfs.
90 This mount.nfs binary should be installed at /sbin/mount.nfs as follows:
[all …]
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 15 which will tell the kernel to mount the root file system over the
18 In order to mount, the network stack will also need to be set up by
22 A CIFS root mount currently requires the use of SMB1+UNIX Extensions
31 to use can nonetheless be changed via the 'vers=' mount option. This
52 This is just a virtual device that basically tells the kernel to mount
59 Enables the kernel to mount the root file system via SMB that are
62 The default mount options are set in fs/smb/client/cifsroot.c.
71 Optional mount options. For more information, see mount.cifs(8).
|
| /Documentation/cdrom/ |
| D | packet-writing.rst | 25 - Now you can mount /dev/pktcdvd/dev_name and copy files to it. Enjoy::
27 # mount /dev/pktcdvd/dev_name /cdrom -t udf -o rw,noatime
42 # mount /dev/pktcdvd/dev_name /cdrom -t udf -o rw,noatime
56 # mount /dev/hdc /cdrom -t udf -o rw,noatime
69 # mount /dev/pktcdvd/dev_name /cdrom -t udf -o rw,noatime
85 use the noatime mount option.
111 # mount -t udf -o rw,noatime /dev/pktcdvd/dev_name /dvdram
|
| /Documentation/bpf/ |
| D | s390.rst | 31 sudo mount --rbind /dev ./s390-toolchain/dev
32 sudo mount --rbind /proc ./s390-toolchain/proc
33 sudo mount --rbind /sys ./s390-toolchain/sys
77 The disk image can be prepared using a loopback mount and debootstrap::
83 sudo mount /dev/loopX ./s390.rootfs
156 mount -t 9p linux /linux
157 mount -t proc proc /proc
158 mount -t sysfs sys /sys
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-virtiofs | 5 [RO] The mount "tag" that can be used to mount this filesystem.
|
1234567891011