aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/fuse.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/filesystems/fuse.txt')
-rw-r--r--Documentation/filesystems/fuse.txt25
1 files changed, 23 insertions, 2 deletions
diff --git a/Documentation/filesystems/fuse.txt b/Documentation/filesystems/fuse.txt
index a584f05403a4..345392c4caeb 100644
--- a/Documentation/filesystems/fuse.txt
+++ b/Documentation/filesystems/fuse.txt
@@ -51,6 +51,22 @@ homepage:
51 51
52 http://fuse.sourceforge.net/ 52 http://fuse.sourceforge.net/
53 53
54Filesystem type
55~~~~~~~~~~~~~~~
56
57The filesystem type given to mount(2) can be one of the following:
58
59'fuse'
60
61 This is the usual way to mount a FUSE filesystem. The first
62 argument of the mount system call may contain an arbitrary string,
63 which is not interpreted by the kernel.
64
65'fuseblk'
66
67 The filesystem is block device based. The first argument of the
68 mount system call is interpreted as the name of the device.
69
54Mount options 70Mount options
55~~~~~~~~~~~~~ 71~~~~~~~~~~~~~
56 72
@@ -94,6 +110,11 @@ Mount options
94 The default is infinite. Note that the size of read requests is 110 The default is infinite. Note that the size of read requests is
95 limited anyway to 32 pages (which is 128kbyte on i386). 111 limited anyway to 32 pages (which is 128kbyte on i386).
96 112
113'blksize=N'
114
115 Set the block size for the filesystem. The default is 512. This
116 option is only valid for 'fuseblk' type mounts.
117
97Control filesystem 118Control filesystem
98~~~~~~~~~~~~~~~~~~ 119~~~~~~~~~~~~~~~~~~
99 120
@@ -111,7 +132,7 @@ For each connection the following files exist within this directory:
111 132
112 'waiting' 133 'waiting'
113 134
114 The number of requests which are waiting to be transfered to 135 The number of requests which are waiting to be transferred to
115 userspace or being processed by the filesystem daemon. If there is 136 userspace or being processed by the filesystem daemon. If there is
116 no filesystem activity and 'waiting' is non-zero, then the 137 no filesystem activity and 'waiting' is non-zero, then the
117 filesystem is hung or deadlocked. 138 filesystem is hung or deadlocked.
@@ -136,7 +157,7 @@ following will happen:
136 157
137 2) If the request is not yet sent to userspace AND the signal is not 158 2) If the request is not yet sent to userspace AND the signal is not
138 fatal, then an 'interrupted' flag is set for the request. When 159 fatal, then an 'interrupted' flag is set for the request. When
139 the request has been successfully transfered to userspace and 160 the request has been successfully transferred to userspace and
140 this flag is set, an INTERRUPT request is queued. 161 this flag is set, an INTERRUPT request is queued.
141 162
142 3) If the request is already sent to userspace, then an INTERRUPT 163 3) If the request is already sent to userspace, then an INTERRUPT