mirror of
https://github.com/torvalds/linux.git
synced 2025-10-29 07:46:20 +02:00
docs: Remove remainders of reiserfs
Reiserfs has been removed in 6.13, there are still some mentions in the documentation about it and the tools. Remove those that don't seem relevant anymore but keep references to reiserfs' r5 hash used by some code. There's one change in a script scripts/selinux/install_policy.sh but it does not seem to be relevant either. Signed-off-by: David Sterba <dsterba@suse.com> Acked-by: Paul Moore <paul@paul-moore.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> Link: https://lore.kernel.org/r/20250813100053.1291961-1-dsterba@suse.com
This commit is contained in:
David Sterba
Jonathan Corbet
parent
4e18a0b090
commit
37c52167b0
6 changed files with 7 additions and 22 deletions
|
|
@ -398,7 +398,7 @@ There are 3 different data modes:
|
|||
* writeback mode
|
||||
|
||||
In data=writeback mode, ext4 does not journal data at all. This mode provides
|
||||
a similar level of journaling as that of XFS, JFS, and ReiserFS in its default
|
||||
a similar level of journaling as that of XFS and JFS in its default
|
||||
mode - metadata journaling. A crash+recovery can cause incorrect data to
|
||||
appear in files which were written shortly before the crash. This mode will
|
||||
typically provide the best ext4 performance.
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ Caveats
|
|||
Check your drive's rating, and don't wear down your drive's lifetime if you
|
||||
don't need to.
|
||||
|
||||
* If you mount some of your ext3/reiserfs filesystems with the -n option, then
|
||||
* If you mount some of your ext3 filesystems with the -n option, then
|
||||
the control script will not be able to remount them correctly. You must set
|
||||
DO_REMOUNTS=0 in the control script, otherwise it will remount them with the
|
||||
wrong options -- or it will fail because it cannot write to /etc/mtab.
|
||||
|
|
@ -96,7 +96,7 @@ control script increases dirty_expire_centisecs and dirty_writeback_centisecs in
|
|||
dirtied are not forced to be written to disk as often. The control script also
|
||||
changes the dirty background ratio, so that background writeback of dirty pages
|
||||
is not done anymore. Combined with a higher commit value (also 10 minutes) for
|
||||
ext3 or ReiserFS filesystems (also done automatically by the control script),
|
||||
ext3 filesystem (also done automatically by the control script),
|
||||
this results in concentration of disk activity in a small time interval which
|
||||
occurs only once every 10 minutes, or whenever the disk is forced to spin up by
|
||||
a cache miss. The disk can then be spun down in the periods of inactivity.
|
||||
|
|
@ -587,7 +587,7 @@ Control script::
|
|||
FST=$(deduce_fstype $MP)
|
||||
fi
|
||||
case "$FST" in
|
||||
"ext3"|"reiserfs")
|
||||
"ext3")
|
||||
PARSEDOPTS="$(parse_mount_opts commit "$OPTS")"
|
||||
mount $DEV -t $FST $MP -o remount,$PARSEDOPTS,commit=$MAX_AGE$NOATIME_OPT
|
||||
;;
|
||||
|
|
@ -647,7 +647,7 @@ Control script::
|
|||
FST=$(deduce_fstype $MP)
|
||||
fi
|
||||
case "$FST" in
|
||||
"ext3"|"reiserfs")
|
||||
"ext3")
|
||||
PARSEDOPTS="$(parse_mount_opts_wfstab $DEV commit $OPTS)"
|
||||
PARSEDOPTS="$(parse_yesno_opts_wfstab $DEV atime atime $PARSEDOPTS)"
|
||||
mount $DEV -t $FST $MP -o remount,$PARSEDOPTS
|
||||
|
|
|
|||
|
|
@ -315,7 +315,6 @@ network daemons and file systems that didn't need to be disturbed.
|
|||
ideally, the reset should happen at or below the block layer,
|
||||
so that the file systems are not disturbed.
|
||||
|
||||
Reiserfs does not tolerate errors returned from the block device.
|
||||
Ext3fs seems to be tolerant, retrying reads/writes until it does
|
||||
succeed. Both have been only lightly tested in this scenario.
|
||||
|
||||
|
|
|
|||
|
|
@ -46,7 +46,6 @@ util-linux 2.10o mount --version
|
|||
kmod 13 depmod -V
|
||||
e2fsprogs 1.41.4 e2fsck -V
|
||||
jfsutils 1.1.3 fsck.jfs -V
|
||||
reiserfsprogs 3.6.3 reiserfsck -V
|
||||
xfsprogs 2.6.0 xfs_db -V
|
||||
squashfs-tools 4.0 mksquashfs -version
|
||||
btrfs-progs 0.18 btrfsck
|
||||
|
|
@ -260,14 +259,6 @@ Sono disponibili i seguenti strumenti:
|
|||
|
||||
- sono disponibili altri strumenti per il file-system.
|
||||
|
||||
Reiserfsprogs
|
||||
-------------
|
||||
|
||||
Il pacchetto reiserfsprogs dovrebbe essere usato con reiserfs-3.6.x (Linux
|
||||
kernel 2.4.x). Questo è un pacchetto combinato che contiene versioni
|
||||
funzionanti di ``mkreiserfs``, ``resize_reiserfs``, ``debugreiserfs`` e
|
||||
``reiserfsck``. Questi programmi funzionano sulle piattaforme i386 e alpha.
|
||||
|
||||
Xfsprogs
|
||||
--------
|
||||
|
||||
|
|
@ -479,11 +470,6 @@ JFSutils
|
|||
|
||||
- <https://jfs.sourceforge.net/>
|
||||
|
||||
Reiserfsprogs
|
||||
-------------
|
||||
|
||||
- <https://git.kernel.org/pub/scm/linux/kernel/git/jeffm/reiserfsprogs.git/>
|
||||
|
||||
Xfsprogs
|
||||
--------
|
||||
|
||||
|
|
|
|||
|
|
@ -5460,7 +5460,7 @@ struct btrfs_dir_list {
|
|||
* See process_dir_items_leaf() for details about why it is needed.
|
||||
* This is a recursive operation - if an existing dentry corresponds to a
|
||||
* directory, that directory's new entries are logged too (same behaviour as
|
||||
* ext3/4, xfs, f2fs, reiserfs, nilfs2). Note that when logging the inodes
|
||||
* ext3/4, xfs, f2fs, nilfs2). Note that when logging the inodes
|
||||
* the dentries point to we do not acquire their VFS lock, otherwise lockdep
|
||||
* complains about the following circular lock dependency / possible deadlock:
|
||||
*
|
||||
|
|
|
|||
|
|
@ -74,7 +74,7 @@ cd /etc/selinux/dummy/contexts/files
|
|||
$SF -F file_contexts /
|
||||
|
||||
mounts=`cat /proc/$$/mounts | \
|
||||
grep -E "ext[234]|jfs|xfs|reiserfs|jffs2|gfs2|btrfs|f2fs|ocfs2" | \
|
||||
grep -E "ext[234]|jfs|xfs|jffs2|gfs2|btrfs|f2fs|ocfs2" | \
|
||||
awk '{ print $2 '}`
|
||||
$SF -F file_contexts $mounts
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue