doc: filesystems : Fix typo in Documentations/filesystems
Correct spelling typo in Documentations/filesystems. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Acked-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
This commit is contained in:
parent
3948ff8bba
commit
9ed354b732
|
@ -87,7 +87,7 @@ Unless otherwise specified, all options default to off.
|
||||||
|
|
||||||
device=<devicepath>
|
device=<devicepath>
|
||||||
Specify a device during mount so that ioctls on the control device
|
Specify a device during mount so that ioctls on the control device
|
||||||
can be avoided. Especialy useful when trying to mount a multi-device
|
can be avoided. Especially useful when trying to mount a multi-device
|
||||||
setup as root. May be specified multiple times for multiple devices.
|
setup as root. May be specified multiple times for multiple devices.
|
||||||
|
|
||||||
discard
|
discard
|
||||||
|
|
|
@ -93,7 +93,7 @@ For a filesystem to be exportable it must:
|
||||||
2/ make sure that d_splice_alias is used rather than d_add
|
2/ make sure that d_splice_alias is used rather than d_add
|
||||||
when ->lookup finds an inode for a given parent and name.
|
when ->lookup finds an inode for a given parent and name.
|
||||||
|
|
||||||
If inode is NULL, d_splice_alias(inode, dentry) is eqivalent to
|
If inode is NULL, d_splice_alias(inode, dentry) is equivalent to
|
||||||
|
|
||||||
d_add(dentry, inode), NULL
|
d_add(dentry, inode), NULL
|
||||||
|
|
||||||
|
|
|
@ -149,7 +149,7 @@ Bitmap system area
|
||||||
------------------
|
------------------
|
||||||
|
|
||||||
The bitmap itself is divided into three parts.
|
The bitmap itself is divided into three parts.
|
||||||
First the system area, that is split into two halfs.
|
First the system area, that is split into two halves.
|
||||||
Then userspace.
|
Then userspace.
|
||||||
|
|
||||||
The requirement for a static, fixed preallocated system area comes from how
|
The requirement for a static, fixed preallocated system area comes from how
|
||||||
|
|
|
@ -135,7 +135,7 @@ default behaviour.
|
||||||
If the memory cost of 8 log buffers is too high on small
|
If the memory cost of 8 log buffers is too high on small
|
||||||
systems, then it may be reduced at some cost to performance
|
systems, then it may be reduced at some cost to performance
|
||||||
on metadata intensive workloads. The logbsize option below
|
on metadata intensive workloads. The logbsize option below
|
||||||
controls the size of each buffer and so is also relevent to
|
controls the size of each buffer and so is also relevant to
|
||||||
this case.
|
this case.
|
||||||
|
|
||||||
logbsize=value
|
logbsize=value
|
||||||
|
|
Loading…
Reference in New Issue