mirror of
https://github.com/torvalds/linux
synced 2024-11-05 18:23:50 +00:00
571640cad3
I can't think of any valid reason for ext4 to not use barriers when they are available; I believe this is necessary for filesystem integrity in the face of a volatile write cache on storage. An administrator who trusts that the cache is sufficiently battery- backed (and power supplies are sufficiently redundant, etc...) can always turn it back off again. SuSE has carried such a patch for ext3 for quite some time now. Also document the mount option while we're at it. Signed-off-by: Eric Sandeen <sandeen@redhat.com> Signed-off-by: Mingming Cao <cmm@us.ibm.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> |
||
---|---|---|
.. | ||
configfs | ||
00-INDEX | ||
9p.txt | ||
adfs.txt | ||
affs.txt | ||
afs.txt | ||
automount-support.txt | ||
befs.txt | ||
bfs.txt | ||
cifs.txt | ||
coda.txt | ||
cramfs.txt | ||
dentry-locking.txt | ||
directory-locking | ||
dlmfs.txt | ||
dnotify.txt | ||
ecryptfs.txt | ||
Exporting | ||
ext2.txt | ||
ext3.txt | ||
ext4.txt | ||
files.txt | ||
fuse.txt | ||
gfs2.txt | ||
hfs.txt | ||
hfsplus.txt | ||
hpfs.txt | ||
inotify.txt | ||
isofs.txt | ||
jfs.txt | ||
Locking | ||
locks.txt | ||
mandatory-locking.txt | ||
ncpfs.txt | ||
nfs-rdma.txt | ||
nfsroot.txt | ||
ntfs.txt | ||
ocfs2.txt | ||
porting | ||
proc.txt | ||
quota.txt | ||
ramfs-rootfs-initramfs.txt | ||
relay.txt | ||
romfs.txt | ||
rpc-cache.txt | ||
seq_file.txt | ||
sharedsubtree.txt | ||
smbfs.txt | ||
spufs.txt | ||
sysfs-pci.txt | ||
sysfs.txt | ||
sysv-fs.txt | ||
tmpfs.txt | ||
udf.txt | ||
ufs.txt | ||
vfat.txt | ||
vfs.txt | ||
xfs.txt | ||
xip.txt |