1REISERFSTUNE(8) System Manager's Manual REISERFSTUNE(8)
2
3
4
6 reiserfstune - The tunning tool for the ReiserFS filesystem.
7
9 reiserfstune [ -f ] [ -h | --help ] [ -j | --journal-device FILE ] [
10 --no-journal-available ] [ --journal-new-device FILE ] [ --make-jour‐
11 nal-standard ] [ -s | --journal-new-size N ] [ -o | --journal-new-off‐
12 set N ] [ -t | --max-transaction-size N ] [ -b | --add-badblocks file ]
13 [ -B | --badblocks file ] [ -u | --uuid UUID ] [ -l | --label LABEL ] [
14 -c | --check-interval interval-in-days ] [ -C | --time-last-checked
15 timestamp ] [ -m | --max-mnt-count count ] [ -M | --mnt-count count ]
16 device
17
19 reiserfstune is used for tuning the ReiserFS. It can change two journal
20 parameters (the journal size and the maximum transaction size), and it
21 can move the journal's location to a new specified block device. (The
22 old ReiserFS's journal may be kept unused, or discarded at the user's
23 option.) Besides that reiserfstune can store the bad block list to the
24 ReiserFS and set UUID and LABEL. Note: At the time of writing the
25 relocated journal was implemented for a special release of ReiserFS,
26 and was not expected to be put into the mainstream kernel until approx‐
27 imately Linux 2.5. This means that if you have the stock kernel you
28 must apply a special patch. Without this patch the kernel will refuse
29 to mount the newly modified file system. We will charge $25 to explain
30 this to you if you ask us why it doesn't work.
31
32 Perhaps the most interesting application of this code is to put the
33 journal on a solid state disk.
34
35 device is the special file corresponding to the newly specified block
36 device (e.g /dev/hdXX for IDE disk partition or /dev/sdXX for
37 the SCSI disk partition).
38
40 -h | --help
41 Print usage information and exit.
42
43 -j | --journal-device FILE
44 FILE is the file name of the block device the file system has
45 the current journal (the one prior to running reiserfstune) on.
46 This option is required when the journal is already on a sepa‐
47 rate device from the main data device (although it can be
48 avoided with --no-journal-available). If you don't specify jour‐
49 nal device by this option, reiserfstune suppose that journal is
50 on main device.
51
52 --no-journal-available
53 allows reiserfstune to continue when the current journal's block
54 device is no longer available. This might happen if a disk goes
55 bad and you remove it (and run fsck).
56
57 --journal-new-device FILE
58 FILE is the file name of the block device which will contain the
59 new journal for the file system. If you don't specify this,
60 reiserfstune supposes that journal device remains the
61 same.
62
63 -s | --journal-new-size N
64 N is the size parameter for the new journal. When journal is to
65 be on a separate device - its size defaults to number of blocks
66 that device has. When journal is to be on the same device as the
67 filesytem - its size defaults to amount of blocks allocated for
68 journal by mkreiserfs when it created the filesystem. Minimum is
69 513 for both cases.
70
71 -o | --journal-new-offset N
72 N is an offset in blocks where journal will starts from when
73 journal is to be on a separate device. Default is 0. Has no
74 effect when journal is to be on the same device as the filesys‐
75 tem. Most users have no need to use this feature. It can be
76 used when you want the journals from multiple filesystems to
77 reside on the same device, and you don't want to or cannot par‐
78 tition that device.
79
80 -t | --maximal-transaction-size N
81 N is the maximum transaction size parameter for the new journal.
82 The default, and max possible, value is 1024 blocks. It should
83 be less than half the size of the journal. If specifed incor‐
84 rectly, it will be adjusted.
85
86 -b | --add-badblocks file
87 File is the file name of the file that contains the list of
88 blocks to be marked as bad on the fs. The list is added to the
89 fs list of bad blocks.
90
91 -B | --badblocks file
92 File is the file name of the file that contains the list of
93 blocks to be marked as bad on the fs. The bad block list on the
94 fs is cleared before the list specified in the File is added to
95 the fs.
96
97 -f | --force
98 Normally reiserfstune will refuse to change a journal of a file
99 system that was created before this journal relocation code.
100 This is because if you change the journal, you cannot go back
101 (without special option --make-journal-standard) to an old ker‐
102 nel that lacks this feature and be able to use your filesytem.
103 This option forces it to do that. Specified more than once it
104 allows to avoid asking for confirmation.
105
106 --make-journal-standard
107 As it was mentioned above, if your file system has non-standard
108 journal, it can not be mounted on the kernel without journal
109 relocation code. The thing can be changed, the only condition is
110 that there is reserved area on main device of the standard jour‐
111 nal size 8193 blocks (it will be so for instance if you convert
112 standard journal to non-standard). Just specify this option when
113 you relocate journal back, or without relocation if you already
114 have it on main device.
115
116 -u | --uuid UUID
117 Set the universally unique identifier ( UUID ) of the
118 filesystem to UUID (see also uuidgen(8)). The format of the
119 UUID is a series of hex digits separated by hypthens,
120 like this: "c1b9d5a2-f162-11cf-9ece-0020afc76f16".
121
122 -l | --label LABEL
123 Set the volume label of the filesystem. LABEL can be at
124 most 16 characters long; if it is longer than 16 characters,
125 reiserfstune will truncate it.
126
127 -c | --check-interval interval-in-days
128 Adjust the maximal time between two filesystem checks. A value
129 of "disable" will disable the time-dependent checking. A value
130 of "default" will restore the compile-time default.
131
132 It is strongly recommended that either -m (mount-count depen‐
133 dent) or -c (time-dependent) checking be enabled to force peri‐
134 odic full fsck.reiserfs(8) checking of the filesystem. Failure
135 to do so may lead to filesystem corruption (due to bad disks,
136 cables, memory, or kernel bugs) going unnoticed, ultimately
137 resulting in data loss or corruption.
138
139 -C | --time-last-checked timestamp
140 Set the time the filesystem was last checked using fsck.reis‐
141 erfs. This can be useful in scripts which use a Logical Volume
142 Manager to make a consistent snapshot of a filesystem, and then
143 check the filesystem during off hours to make sure it hasn't
144 been corrupted due to hardware problems, etc. If the filesystem
145 was clean, then this option can be used to set the last checked
146 time on the original filesystem. The format of time-last-checked
147 is the international date format, with an optional time speci‐
148 fier, i.e. YYYYMMDD[HH[MM[SS]]]. The keyword now is also
149 accepted, in which case the last checked time will be set to the
150 current time.
151
152 -m | --max-mnt-count max-mount-count
153 Adjust the number of mounts after which the filesystem will be
154 checked by fsck.reiserfs(8). If max-mount-count is "disable",
155 the number of times the filesystem is mounted will be disre‐
156 garded by fsck.reiserfs(8) and the kernel. A value of "default"
157 will restore the compile-time default.
158
159 Staggering the mount-counts at which filesystems are forcibly
160 checked will avoid all filesystems being checked at one time
161 when using journaled filesystems.
162
163 You should strongly consider the consequences of disabling
164 mount-count-dependent checking entirely. Bad disk drives,
165 cables, memory, and kernel bugs could all corrupt a filesystem
166 without marking the filesystem dirty or in error. If you are
167 using journaling on your filesystem, your filesystem will never
168 be marked dirty, so it will not normally be checked. A filesys‐
169 tem error detected by the kernel will still force an fsck on the
170 next reboot, but it may already be too late to prevent data loss
171 at that point.
172
173 This option requires a kernel which supports incrementing the
174 count on each mount. This feature has not been incorporated into
175 kernel versions older than 2.6.25.
176
177 See also the -c option for time-dependent checking.
178
179 -M | --mnt-count count
180 Set the number of times the filesystem has been mounted. If set
181 to a greater value than the max-mount-counts parameter set by
182 the -m option, fsck.reiserfs(8) will check the filesystem at the
183 next reboot.
184
186 1. You have ReiserFS on /dev/hda1, and you wish to have it working with
187 its journal on the device /dev/journal
188
189 boot kernel patched with special "relocatable journal support" patch
190 reiserfstune /dev/hda1 --journal-new-device /dev/journal -f
191 mount /dev/hda1 and use.
192 You would like to change max transaction size to 512 blocks
193 reiserfstune -t 512 /dev/hda1
194 You would like to use your file system on another kernel that doesn't
195 contain relocatable journal support.
196 umount /dev/hda1
197 reiserfstune /dev/hda1 -j /dev/journal --journal-new-device /dev/hda1 --make-journal-standard
198 mount /dev/hda1 and use.
199
200 2. You would like to have ReiserFS on /dev/hda1 and to be able to
201 switch between different journals including journal located on the
202 device containing the filesystem.
203
204 boot kernel patched with special "relocatable journal support" patch
205 mkreiserfs /dev/hda1
206 you got solid state disk (perhaps /dev/sda, they typically look like scsi disks)
207 reiserfstune --journal-new-device /dev/sda1 -f /dev/hda1
208 Your scsi device dies, it is three in the morning, you have an extra IDE device
209 lying around
210 reiserfsck --no-journal-available /dev/hda1
211 or
212 reiserfsck --rebuild-tree --no-journal-available /dev/hda1
213 reiserfstune --no-journal-available --journal-new-device /dev/hda1 /dev/hda1
214 using /dev/hda1 under patched kernel
215
217 This version of reiserfstune has been written by Vladimir Demidov
218 <vova@namesys.com> and Edward Shishkin <edward@namesys.com>.
219
221 Please report bugs to the ReiserFS developers <reiserfs-
222 devel@vger.kerne.org>, providing as much information as possible--your
223 hardware, kernel, patches, settings, all printed messages; check the
224 syslog file for any related information.
225
227 reiserfsck(8), debugreiserfs(8), mkreiserfs(8)
228
229
230
231
232
233Reiserfsprogs-3.6.27 January 2009 REISERFSTUNE(8)