2 .\" Copyright 1993, 1994, 1995 by Theodore Ts'o. All Rights Reserved.
3 .\" This file may be copied under the terms of the GNU Public License.
5 .\" Japanese Version Copyright 1998 by MATSUMOTO Shoji. All Rights Reserved.
6 .\" Translated Thu Mar 12 12:06:45 JST 1998 by MATSUMOTO Shoji.
7 .\" Updated Sat 23 Oct 1999 by NAKANO Takeo <nakano@apm.seikei.ac.jp>
8 .\" Updated Tue 16 Nov 1999 by NAKANO Takeo
9 .\" Updated & Modified Tue Aug 7 08:35:46 JST 2001
10 .\" by Yuichi SATO <ysato@h4.dion.ne.jp>
11 .\" Updated & Modified Sun Sep 9 22:13:00 JST 2001 by Yuichi SATO
12 .\" Updated Fri 4 Oct 2002 by NAKANO Takeo
13 .\" Updated & Modified Sat Apr 17 02:08:36 JST 2004
14 .\" by Yuichi SATO <ysato444@yahoo.co.jp>
15 .\" Updated & Modified Tue Dec 20 06:30:28 JST 2005 by Yuichi SATO
16 .\" Updated & Modified Sun Oct 29 02:07:11 JST 2006 by Yuichi SATO
18 .\"WORD: fatal error Ã×̿Ū¤Ê¥¨¥é¡¼(fatal error)
19 .\"WORD: bad block ÉÔÎÉ¥Ö¥í¥Ã¥¯
20 .\"WORD: non-interactively ÈóÂÐÏÃŪ¤Ë
21 .\"WORD: byte-swap ¥Ð¥¤¥È¥¹¥ï¥Ã¥×(¥¨¥ó¥Ç¥£¥¢¥ó)
22 .\"WORD: byte-order ¥Ð¥¤¥È¥ª¡¼¥À¡¼
23 .\"WORD: statistics Åý·×(statistisc)
24 .\"WORD: verbose ¾ÜºÙ¤Ê
25 .\"WORD: REPORTING BUGS ¥Ð¥°Êó¹ð
26 .\"WORD: crush ¥¯¥é¥Ã¥·¥å
27 .\"WORD: reboot ¥ê¥Ö¡¼¥È
28 .\"WORD: transcript ¼Â¹ÔµÏ¿
30 .TH E2FSCK 8 "May 2006" "E2fsprogs version 1.39"
32 .\"O e2fsck \- check a Linux ext2/ext3 file system
34 e2fsck \- Linux ext2/ext3 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Á¥§¥Ã¥¯¤¹¤ë
69 .\"O is used to check a Linux second extended file system (ext2fs).
72 .\"O supports ext2 filesystems containing a journal, which are
73 .\"O also sometimes known as ext3 filesystems, by first applying the journal
74 .\"O to the filesystem before continuing with normal
76 .\"O processing. After the journal has been applied, a filesystem will
77 .\"O normally be marked as clean. Hence, for ext3 filesystems,
79 .\"O will normally run the journal and exit, unless its superblock
80 .\"O indicates that further checking is required.
82 ¤Ï Linux Âè 2 ³ÈÄ¥¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à (ext2fs) ¤ò¥Á¥§¥Ã¥¯¤¹¤ë¡£
83 e2fsck ¤Ï¥¸¥ã¡¼¥Ê¥ëÉÕ¤¤Î ext2 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤â¥µ¥Ý¡¼¥È¤¹¤ë¡£
84 ¤³¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï ext3 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤È¤â¸Æ¤Ð¤ì¡¢
87 ½èÍý¤ò¹Ô¤¦Á°¤Ë¡¢¤Þ¤º¥¸¥ã¡¼¥Ê¥ë¤ò¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËŬÍѤ¹¤ë¡£
88 ¥¸¥ã¡¼¥Ê¥ë¤òŬÍѤ·¤¿¸å¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÏÄ̾ï
89 clean ¤Ç¤¢¤ë¤È¥Þ¡¼¥¯¤µ¤ì¤ë¡£
90 ¤è¤Ã¤Æ¡¢ext3 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ·¤Æ¤Ï¡¢
92 ¤ÏÄ̾兩¥ã¡¼¥Ê¥ë¤ò¼Â¹Ô¤·¤Æ½ªÎ»¤¹¤ë¤À¤±¤Ë¤Ê¤ë
93 (¤¿¤À¤·¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤Ë¡¢
94 ¤è¤ê¾ÜºÙ¤Ê¥Á¥§¥Ã¥¯¤òÍ׵᤹¤ëÆâÍƤ¬µ½Ò¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤ÏÊÌ)¡£
97 .\"O is the device file where the filesystem is stored (e.g.
100 ¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬Êݸ¤µ¤ì¤Æ¤¤¤ë¥Ç¥Ð¥¤¥¹¥Õ¥¡¥¤¥ë¤Ç¤¢¤ë (Îã:
103 .\"O Note that in general it is not safe to run
105 .\"O on mounted filesystems. The only exception is if the
107 .\"O option is specified, and
114 .\"O specified. However, even if it is safe to do so, the results printed by
116 .\"O are not valid if the filesystem is mounted. If
118 .\"O asks whether or not you should check a filesystem which is mounted,
119 .\"O the only correct answer is ``no''. Only experts who really know what
120 .\"O they are doing should consider answering this question in any other way.
121 ¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ËÂФ·¤Æ
123 ¤ò¼Â¹Ô¤¹¤ë¤Î¤Ï¡¢°ìÈÌŪ¤Ë¸À¤Ã¤Æ¡¢°ÂÁ´¤Ç¤Ê¤¤¤È¤¤¤¦ÅÀ¤ËÃí°Õ¤¹¤ë¤³¤È¡£
126 ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Æ¡¢¤«¤Ä
130 ¥ª¥×¥·¥ç¥ó¤¬»ØÄꤵ¤ì¤Æ\fI¤¤¤Ê¤¤\fR¾ì¹ç¤Ç¤¢¤ë¡£
131 ¤·¤«¤·°ÂÁ´¤Ë¼Â¹Ô¤Ç¤¤¿¤È¤·¤Æ¤â¡¢
132 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤ë¤È¤¤Ë
134 ¤Çɽ¼¨¤µ¤ì¤ë·ë²Ì¤Ï͸ú¤Ç¤Ï¤Ê¤¤¡£
135 ¥Þ¥¦¥ó¥È¤µ¤ì¤Æ¤¤¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¥Á¥§¥Ã¥¯¤¹¤Ù¤¤«Èݤ«¤ò
137 ¤¬¼ÁÌ䤷¤Æ¤¤¿¾ì¹ç¡¢Í£°ì¤ÎÀµ¤·¤¤Åú¤¨¤Ï ``no'' ¤Ç¤¢¤ë¡£
138 ²¿¤ò¤·¤Æ¤¤¤ë¤«¤òËÜÅö¤Ëʬ¤«¤Ã¤Æ¤¤¤ë¥¨¥¥¹¥Ñ¡¼¥È¤Î¤ß¤¬¡¢
139 ¤³¤Î¼ÁÌä¤ËÂФ·¤ÆÊ̤ÎÅú¤¨¤ò½Ð¤¹¤«¤ò¹Í¤¨¤ë¤Ù¤¤Ç¤¢¤ë¡£
144 .\"O This option does the same thing as the
146 .\"O option. It is provided for backwards compatibility only; it is
147 .\"O suggested that people use
149 .\"O option whenever possible.
152 ¥ª¥×¥·¥ç¥ó¤ÈƱÍͤΤâ¤Î¤È¤ß¤Ê¤µ¤ì¤ë¡£
153 ²¼°Ì¸ß´¹À¤Î¤¿¤á¤Ë¤Î¤ß½àÈ÷¤µ¤ì¤Æ¤¤¤ë¥ª¥×¥·¥ç¥ó¤Ç¤¢¤ë¤¿¤á¡¢
156 ¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤³¤È¤¬¿ä¾©¤µ¤ì¤ë¡£
158 .BI \-b " superblock"
159 .\"O Instead of using the normal superblock, use an alternative superblock
161 .\"O .IR superblock .
162 Ä̾ï¤Î¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤Î¤«¤ï¤ê¤Ë¡¢
164 ¤ò¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤È¤·¤ÆÍøÍѤ¹¤ë¡£
165 .\"O This option is normally used when the primary superblock has been
167 ¤³¤Î¥ª¥×¥·¥ç¥ó¤¬ÍѤ¤¤é¤ì¤ë¤Î¤Ï¡¢
168 ¥×¥é¥¤¥Þ¥ê¤Ê¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤¬²õ¤ì¤¿¾ì¹ç¤Ç¤¢¤ë¡£
169 .\"O The location of the backup superblock is dependent on the
170 .\"O filesystem's blocksize. For filesystems with 1k blocksizes, a backup
171 .\"O superblock can be found at block 8193; for filesystems with 2k
172 .\"O blocksizes, at block 16384; and for 4k blocksizes, at block 32768.
173 ¥Ð¥Ã¥¯¥¢¥Ã¥×¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤Î¾ì½ê¤Ï¡¢
174 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤Ë¤è¤Ã¤Æ°Û¤Ê¤ë¡£
175 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤¬ 1k ¤Î¾ì¹ç¡¢
176 ¥Ð¥Ã¥¯¥¢¥Ã¥×¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤Ï 8193 ¤Ë¤¢¤ë¡£
177 ¤Þ¤¿¡¢¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤¬ 2k ¤Î¾ì¹ç¤Ï 16384 ¤Ë¡¢
178 4k ¤Î¾ì¹ç¤Ï 32768 ¤Ë¤¢¤ë¡£
180 .\"O Additional backup superblocks can be determined by using the
182 .\"O program using the
184 .\"O option to print out where the superblocks were created.
185 ¥Ð¥Ã¥¯¥¢¥Ã¥×ÍѤÎÄɲ幡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤Î°ÌÃÖ¤ò·è¤á¤ë¤Ë¤Ï¡¢
189 ¥ª¥×¥·¥ç¥óÉÕ¤¤Ç¼Â¹Ô¤·¤Æ¡¢
190 ¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤¬À¸À®¤µ¤ì¤¿¾ì½ê¤òɽ¼¨¤µ¤»¤ì¤Ð¤è¤¤¡£
195 .\"O which specifies blocksize of the filesystem must be specified in order
196 .\"O for the superblock locations that are printed out to be accurate.
197 ¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤ÎÀµ³Î¤Ê¾ì½ê¤òɽ¼¨¤µ¤»¤¿¤±¤ì¤Ð¡¢
199 ¥ª¥×¥·¥ç¥ó¤Ç¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤ò»ØÄꤷ¤Æ
201 ¤ò¼Â¹Ô¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
203 .\"O If an alternative superblock is specified and
204 .\"O the filesystem is not opened read-only, e2fsck will make sure that the
205 .\"O primary superblock is updated appropriately upon completion of the
206 .\"O filesystem check.
207 ÂåÂØ¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤¬»ØÄꤵ¤ì¡¢
208 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬ read-only °Ê³°¤Ç open ¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¡¢
209 e2fsck ¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Á¥§¥Ã¥¯¤¬½ª¤ï¤Ã¤¿¤È¤¤Ë
210 ¥×¥é¥¤¥Þ¥ê¤Î¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤òŬÀÚ¤ÊÃͤ˹¹¿·¤¹¤ë¤«¤É¤¦¤«¤Î
216 .\"O will search for the superblock at various different
217 .\"O block sizes in an attempt to find the appropriate block size.
218 .\"O This search can be fooled in some cases. This option forces
220 .\"O to only try locating the superblock at a particular blocksize.
221 .\"O If the superblock is not found,
223 .\"O will terminate with a fatal error.
227 ŬÀڤʥ֥í¥Ã¥¯¥µ¥¤¥º¤òõ¤¹¤¿¤á¤Ë
228 ¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤òÍÍ¡¹¤Ê¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤Ç¥µ¡¼¥Á¤¹¤ë¡£
229 ¤³¤Îºî¶È¤Ï̵Â̤ʾì¹ç¤¬¤¢¤ë¡£¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¡¢
230 ¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤ò»ØÄꤷ¤Æ¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤ò¥µ¡¼¥Á¤¹¤ë¤è¤¦»ØÄꤹ¤ë¡£
231 ¥¹¡¼¥Ñ¡¼¥Ö¥í¥Ã¥¯¤¬¸«¤Ä¤«¤é¤Ê¤¤¾ì¹ç¡¢
233 ¤ÏÃ×̿Ū¤Ê¥¨¥é¡¼ (fatal error) ¤Ç½ªÎ»¤¹¤ë¡£
236 .\"O This option causes
239 .\"O .BR badblocks (8)
240 .\"O program to do a read-only scan of the device in order to find any bad
241 .\"O blocks. If any bad blocks are found, they are added to the bad block
242 .\"O inode to prevent them from being allocated to a file or directory. If
243 .\"O this option is specified twice, then the bad block scan will be done
244 .\"O using a non-destructive read-write test.
245 ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢
249 ¤ò»È¤Ã¤Æ¥Ç¥Ð¥¤¥¹¤Î read-only ¥¹¥¥ã¥ó¤ò¹Ô¤¤¡¢ÉÔÎÉ¥Ö¥í¥Ã¥¯¤òõ¤¹¡£
250 ÉÔÎÉ¥Ö¥í¥Ã¥¯¤¬¸«¤Ä¤«¤ë¤È¡¢¤½¤ì¤òÉÔÎÉ¥Ö¥í¥Ã¥¯ inode ¤Ë²Ã¤¨¡¢
251 ¥Õ¥¡¥¤¥ë¤ä¥Ç¥£¥ì¥¯¥È¥ê¤È¤·¤Æ³ÎÊÝ (allocate) ¤µ¤ì¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¡£
252 ¤³¤Î¥ª¥×¥·¥ç¥ó¤¬ 2 ¤Ä»ØÄꤵ¤ì¤ë¤È¡¢
253 ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Î¥¹¥¥ã¥ó¤ÏÈóÇ˲õŪ read-write ¥Æ¥¹¥È¤òÍѤ¤¤Æ¹Ô¤ï¤ì¤ë¡£
256 .\"O This option causes
258 .\"O to write completion information to the specified file descriptor
259 .\"O so that the progress of the filesystem
260 .\"O check can be monitored. This option is typically used by programs
261 .\"O which are running
263 .\"O If the file descriptor specified is 0,
265 .\"O will print a completion bar as it goes about its business. This requires
266 .\"O that e2fsck is running on a video console or terminal.
267 ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È
269 ¤Ïºî¶È¾õ¶·¤ò»ØÄꤷ¤¿¥Õ¥¡¥¤¥ë¥Ç¥£¥¹¥¯¥ê¥×¥¿¤Ë½ñ¤½Ð¤·¡¢
270 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Á¥§¥Ã¥¯¤Î¿Ê¹Ô¾õ¶·¤ò¥â¥Ë¥¿¡¼¤Ç¤¤ë¤è¤¦¤Ë¤¹¤ë¡£
273 ¤òÆ°ºî¤µ¤»¤ë¥×¥í¥°¥é¥à¤«¤éÎɤ¯ÍѤ¤¤é¤ì¤ë¡£
274 »ØÄꤵ¤ì¤¿¥Õ¥¡¥¤¥ë¥Ç¥£¥¹¥¯¥ê¥×¥¿¤¬ 0 ¤Î¾ì¹ç¡¢
276 ¤Ïºî¶È¤ò¿Ê¤á¤ë¤´¤È¤ËËÀ¥°¥é¥Õ¤ò½ÐÎϤ¹¤ë¡£
277 ¤³¤ÎÆ°ºî¤ò¤µ¤»¤ë¤Ë¤Ï¡¢
279 ¤ò¥Ó¥Ç¥ª¥³¥ó¥½¡¼¥ë¤«Ã¼Ëö¤«¤é¼Â¹Ô¤¹¤ëɬÍפ¬¤¢¤ë¡£
282 .\"O Print debugging output (useless unless you are debugging
284 ¥Ç¥Ð¥Ã¥°¾ðÊó¤ò½ÐÎϤ¹¤ë
286 ¤ò¥Ç¥Ð¥Ã¥°¤¹¤ë¤È¤¤Ë¤·¤«Ìò¤ËΩ¤¿¤Ê¤¤)¡£
289 .\"O Optimize directories in filesystem. This option causes e2fsck to
290 .\"O try to optimize all directories, either by reindexing them if the
291 .\"O filesystem supports directory indexing, or by sorting and compressing
292 .\"O directories for smaller directories, or for filesystems using
293 .\"O traditional linear directories.
294 .\"O nakano ¤¿¤Ö¤óºÇ¸å¤Î ,"or" ¤¬Æþ¤ì´Ö°ã¤¤
295 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥àÃæ¤Î¥Ç¥£¥ì¥¯¥È¥ê¤òºÇŬ²½¤¹¤ë¡£
296 ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢
297 e2fsck ¤Ï¤¹¤Ù¤Æ¤Î¥Ç¥£¥ì¥¯¥È¥ê¤òºÇŬ²½¤·¤è¤¦¤È¤¹¤ë¡£
298 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥Ç¥£¥ì¥¯¥È¥ê¥¤¥ó¥Ç¥¯¥·¥ó¥°¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ì¤Ð¡¢
299 ¥¤¥ó¥Ç¥Ã¥¯¥¹¤òºÆÀ¸À®¤¹¤ë¡£
300 ¤Þ¤¿½¾Íè¤ÎÀþ·ÁŪ¤Ê¥Ç¥£¥ì¥¯¥È¥ê¹½Â¤¤ò»È¤¦¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ç¤Ï¡¢
301 ¾®¤µ¤Ê¥Ç¥£¥ì¥¯¥È¥ê¤«¤é½ç¤Ë¥½¡¼¥È¤·¤Æ°µ½Ì¤¹¤ë¡£
303 .BI \-E " extended_options"
304 .\"O Set e2fsck extended options. Extended options are comma
305 .\"O separated, and may take an argument using the equals ('=') sign. The
306 .\"O following options are supported:
307 e2fsck ¤Ë³ÈÄ¥¥ª¥×¥·¥ç¥ó¤òÀßÄꤹ¤ë¡£
308 ³ÈÄ¥¥ª¥×¥·¥ç¥ó´Ö¤Ï¥³¥ó¥Þ¤Ç¶èÀڤꡢ
309 Åù¹æ ('=') ¤Ë³¤±¤ë·Á¤Ç°ú¿ô¤ò¼è¤ë¤³¤È¤â¤Ç¤¤ë¡£
310 ¼¡¤Î¥ª¥×¥·¥ç¥ó¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¡£
313 .BI ea_ver= extended_attribute_version
314 .\"O Assume the format of the extended attribute blocks in the filesystem is
315 .\"O the specified version number. The version number may be 1 or 2. The
316 .\"O default extended attribute version format is 2.
317 .\"O nakano ºÇ¸å¤Îʸ¤Ï version ¤È format ¤¬µÕ¤À¤È»×¤¦¤¬...
318 Âоݥե¡¥¤¥ë¥·¥¹¥Æ¥à¤Î³Èĥ°À¥Ö¥í¥Ã¥¯¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤ò¡¢
319 »ØÄꤷ¤¿¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤Î¤â¤Î¤Ç¤¢¤ë¤È²¾Äꤹ¤ë¡£
320 ¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤Ë¤Ï 1 ¤Þ¤¿¤Ï 2 ¤¬»ØÄê¤Ç¤¤ë¡£
321 ¥Ç¥Õ¥©¥ë¥È¤Î³Èĥ°À¥Õ¥©¡¼¥Þ¥Ã¥È¤Î¥Ð¡¼¥¸¥ç¥ó¤Ï 2 ¤Ç¤¢¤ë¡£
325 .\"O Force checking even if the file system seems clean.
326 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬ clean ¤Ê¾ì¹ç¤Ç¤â¡¢¶¯À©Åª¤Ë¥Á¥§¥Ã¥¯¤¹¤ë¡£
329 .\"O Flush the filesystem device's buffer caches before beginning. Only
330 .\"O really useful for doing
333 ¥Á¥§¥Ã¥¯¤ò»Ï¤á¤ëÁ°¤Ë¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¥Ç¥Ð¥¤¥¹¤Î¥¥ã¥Ã¥·¥å¥Ð¥Ã¥Õ¥¡¤ò
336 ¤òÍѤ¤¤¿¥¿¥¤¥à¥È¥é¥¤¥¢¥ë¤Ë¤Î¤ßÍÍÑ¡£
338 .BI \-j " external-journal"
339 .\"O Set the pathname where the external-journal for this filesystem can be
341 ¤³¤Î¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î³°Éô¥¸¥ã¡¼¥Ê¥ë¤¬¤¢¤ë¥Ñ¥¹Ì¾¤òÀßÄꤹ¤ë¡£
344 .\"O When combined with the
346 .\"O option, any existing bad blocks in the bad blocks list are preserved,
347 .\"O and any new bad blocks found by running
348 .\"O .BR badblocks (8)
349 .\"O will be added to the existing bad blocks list.
351 ¥ª¥×¥·¥ç¥ó¤ÈÁȤ߹ç¤ï¤»¤ë¤È¡¢
352 ÉÔÎÉ¥Ö¥í¥Ã¥¯¥ê¥¹¥È¤Ë¤¢¤ë´û¸¤ÎÉÔÎÉ¥Ö¥í¥Ã¥¯¤ÏÊݸ¤µ¤ì¡¢
354 ¤ò¼Â¹Ô¤·¤Æ¸«¤Ä¤«¤Ã¤¿¿·¤¿¤ÊÉÔÎÉ¥Ö¥í¥Ã¥¯¤¬
355 ´û¸¤ÎÉÔÎÉ¥Ö¥í¥Ã¥¯¥ê¥¹¥È¤ËÄɲ䵤ì¤ë¡£
358 .\"O Add the block numbers listed in the file specified by
360 .\"O to the list of bad blocks. The format of this file is the same as the
361 .\"O one generated by the
362 .\"O .BR badblocks (8)
363 .\"O program. Note that the block numbers are based on the blocksize
364 .\"O of the filesystem. Hence,
365 .\"O .BR badblocks (8)
366 .\"O must be given the blocksize of the filesystem in order to obtain correct
367 .\"O results. As a result, it is much simpler and safer to use the
371 .\"O since it will assure that the correct parameters are passed to the
374 .\"O nakano ¤¤¤Þ¤¤¤Á¥Ô¥ó¤ÈÍè¤Ê¤¤¤±¤É...
376 ¤Ç»ØÄꤷ¤¿¥Õ¥¡¥¤¥ë¤Ë¥ê¥¹¥È¤µ¤ì¤Æ¤¤¤ë¥Ö¥í¥Ã¥¯ÈÖ¹æ¤ò
377 ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Î¥ê¥¹¥È¤ËÄɲ乤롣¤³¤Î¥Õ¥¡¥¤¥ë¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï
379 ¥×¥í¥°¥é¥à¤¬½ÐÎϤ¹¤ë¤â¤Î¤ÈƱ¤¸¤Ç¤¢¤ë¡£
380 ¥Ö¥í¥Ã¥¯ÈÖ¹æ¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤Ë´ð¤Å¤¤¤Æ¤¤¤ë¤³¤È¤ËÃí°Õ¡£
381 ¤·¤¿¤¬¤Ã¤ÆÀµ¤·¤¤·ë²Ì¤òÆÀ¤ë¤¿¤á¤Ë¤Ï
383 ¤Ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤òÍ¿¤¨¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
388 ¥ª¥×¥·¥ç¥ó¤òÍ¿¤¨¤ëÊý¤¬¡¢¤º¤Ã¤Èñ½ã¤«¤Ä°ÂÁ´¤Ç¤¢¤ë¡£
389 ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ì¤Ð¡¢Àµ¤·¤¤¥Ñ¥é¥á¡¼¥¿¤¬
391 ¥×¥í¥°¥é¥à¤ËÅϤ뤳¤È¤Ë¤Ê¤Ã¤Æ¤¤¤ë¡£
394 .\"O Set the bad blocks list to be the list of blocks specified by
396 .\"O (This option is the same as the
398 .\"O option, except the bad blocks list is cleared before the blocks listed
399 .\"O in the file are added to the bad blocks list.)
401 ¤Ç»ØÄꤷ¤¿¥Õ¥¡¥¤¥ë¤Ë½ñ¤«¤ì¤Æ¤¤¤ë¥Ö¥í¥Ã¥¯¥ê¥¹¥È¤ò¡¢
402 ÉÔÎÉ¥Ö¥í¥Ã¥¯¤Î¥ê¥¹¥È¤Ë»ØÄꤹ¤ë¡£
405 ¥ª¥×¥·¥ç¥ó¤È¤Ï°Û¤Ê¤ê¡¢¥Õ¥¡¥¤¥ë¤Ë¥ê¥¹¥È¤µ¤ì¤Æ¤¤¤ë¥Ö¥í¥Ã¥¯¤ò
406 ÉÔÎÉ¥Ö¥í¥Ã¥¯¥ê¥¹¥È¤Ë²Ã¤¨¤ëÁ°¤Ë¡¢
407 ÉÔÎÉ¥Ö¥í¥Ã¥¯¥ê¥¹¥È¤ò¤¤¤Ã¤¿¤ó¥¯¥ê¥¢¤¹¤ë¡£)
410 .\"O Open the filesystem read-only, and assume an answer of `no' to all
411 .\"O questions. Allows
413 .\"O to be used non-interactively. (Note: if the
418 .\"O options are specified in addition to the
420 .\"O option, then the filesystem will be opened read-write, to permit the
421 .\"O bad-blocks list to be updated. However, no other changes will be made
422 .\"O to the filesystem.) This option
423 .\"O may not be specified at the same time as the
428 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò read-only ¤Ç open ¤·¡¢Á´¤Æ¤ÎÌ䤤¤ËÂФ·¤Æ¡Öno¡×¤ÈÅú¤¨¤ë¡£
430 ¤òÈóÂÐÏÃŪ¤ËÆ°ºî¤µ¤»¤ë¤³¤È¤¬¤Ç¤¤ë¡£(Ãí°Õ:
436 ¤Î¤¤¤º¤ì¤«¤Î¥ª¥×¥·¥ç¥ó¤òÉղä·¤¿¾ì¹ç¤Ï¡¢
437 ÉÔÎÉ¥Ö¥í¥Ã¥¯¥ê¥¹¥È¤ò¹¹¿·¤¹¤ë¤¿¤á¤Ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Ï
438 read/write ¤Ç¥ª¡¼¥×¥ó¤µ¤ì¤ë¡£
439 ¤¿¤À¤·¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¼«ÂΤÏÊѹ¹¤µ¤ì¤Ê¤¤¡£)
444 ¥ª¥×¥·¥ç¥ó¤ÈƱ»þ¤Ë»ØÄꤷ¤Æ¤Ï¤Ê¤é¤Ê¤¤¡£
447 .\"O Automatically repair ("preen") the file system. This option will case
449 .\"O to automatically
450 .\"O fix any filesystem problems that can be safely fixed without human
451 .\"O intervention. If
453 .\"O discovers a problem which may require the system administrator
454 .\"O to take additional corrective action,
456 .\"O will print a description of the problem and then exit with the value 4
457 .\"O logically or'ed into the exit code. (See the \fBEXIT CODE\fR section.)
458 .\"O This option is normally used by the system's boot scripts. It may not
459 .\"O be specified at the same time as the
464 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ò¼ÁÌä¤Ê¤·¤Ç¼«Æ°Åª¤Ë½¤Éü (preen) ¤¹¤ë¡£
465 ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤È¡¢
467 ¤Ï°ÂÁ´¤Ë½¤Àµ¤Ç¤¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÌäÂê¤ò¡¢
468 »ÈÍѼԤÈÂÐÏ令º¤Ë¼«Æ°Åª¤Ë½¤Àµ¤¹¤ë¡£
470 ¤Ï¡¢¥·¥¹¥Æ¥à´ÉÍý¼Ô¤¬Ê̤ËÀµ¤·¤¤¹ÔÆ°¤ò¤È¤ëɬÍפΤ¢¤ëÌäÂê¤ò¸«¤Ä¤±¤ë¤È¡¢
471 ÌäÂê¤ÎÀâÌÀ¤òɽ¼¨¤·¡¢ÃÍ 4 ¤ÈÊÖ¤êÃͤÎÏÀÍý OR ¤ò¤È¤Ã¤¿ÃͤǽªÎ»¤¹¤ë¡£
472 (¡Ö\fBÊÖ¤êÃÍ\fR¡×¤Î¥»¥¯¥·¥ç¥ó¤ò»²¾È¤¹¤ë¤³¤È¡£)
473 Ä̾¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥·¥¹¥Æ¥à¤Î¥Ö¡¼¥È¥¹¥¯¥ê¥×¥È¤Ç»È¤ï¤ì¤ë¡£
478 ¥ª¥×¥·¥ç¥ó¤ÈƱ»þ¤Ë»ØÄꤷ¤Æ¤Ï¤Ê¤é¤Ê¤¤¡£
481 .\"O This option does nothing at all; it is provided only for backwards
483 ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï²¿¤â¤·¤Ê¤¤¡£
484 ²áµî¤È¤Î¸ß´¹À¤Î¤¿¤á¤Ë½àÈ÷¤µ¤ì¤Æ¤¤¤ë¤À¤±¤Ç¤¢¤ë¡£
487 .\"O This option will byte-swap the filesystem so that it is using the normalized,
488 .\"O standard byte-order (which is i386 or little endian). If the filesystem is
489 .\"O already in the standard byte-order,
491 .\"O will take no action.
492 ¤³¤Î¥ª¥×¥·¥ç¥ó¤Ï¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥Ð¥¤¥È¥¹¥ï¥Ã¥× (¥¨¥ó¥Ç¥£¥¢¥ó¤ÎÊѹ¹) ¤ò¹Ô¤¦¡£
493 ¤¹¤Ê¤ï¤Á¡¢i386 ¤ä¥ê¥È¥ë¥¨¥ó¥Ç¥£¥¢¥ó¤Çɸ½àŪ¤Ê¥Ð¥¤¥È¥ª¡¼¥À¡¼¤Ë¤¹¤ë¡£
494 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¤¹¤Ç¤Ëɸ½àŪ¤Ê¥Ð¥¤¥È¥ª¡¼¥À¡¼¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤Ê¤é¤Ð¡¢
499 .\"O This option will byte-swap the filesystem, regardless of its current
501 ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¥Ð¥¤¥È¥¹¥ï¥Ã¥×¤µ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ç¤â¡¢
502 ¸½ºß¤Î¥Ð¥¤¥È¥ª¡¼¥À¡¼¤òÊݤġ£
505 .\"O Print timing statistics for
507 .\"O If this option is used twice, additional timing statistics are printed
508 .\"O on a pass by pass basis.
509 .\"O nakano pass by pass basis ¤È¤Ï?
511 ¤Î¥¿¥¤¥ß¥ó¥°Åý·× (statistics) ¤òɽ¼¨¤¹¤ë¡£
512 ¤³¤Î¥ª¥×¥·¥ç¥ó¤ò 2 ¤Ä»ØÄꤹ¤ë¤È¡¢¤è¤ê¾ÜºÙ¤Ê¥¿¥¤¥ß¥ó¥°Åý·×¤¬
520 .\"O Print version information and exit.
521 ¥Ð¡¼¥¸¥ç¥ó¾ðÊó¤òɽ¼¨¤·¤Æ½ªÎ»¤¹¤ë¡£
524 .\"O Assume an answer of `yes' to all questions; allows
526 .\"O to be used non-interactively. This option
527 .\"O may not be specified at the same time as the
532 Á´¤Æ¤ÎÌ䤤¤ËÂФ·¤Æ¡Öyes¡×¤ÈÅú¤¨¤ë¡£¤³¤ì¤Ë¤è¤Ã¤Æ
534 ¤òÈóÂÐÏÃŪ¤ËÆ°ºî¤µ¤»¤ë¤³¤È¤¬¤Ç¤¤ë¡£
539 ¥ª¥×¥·¥ç¥ó¤ÈƱ»þ¤Ë»ØÄꤷ¤Æ¤Ï¤Ê¤é¤Ê¤¤¡£
542 .\"O The exit code returned by
544 .\"O is the sum of the following conditions:
546 ¤ÎÊÖ¤êÃͤϡ¢°Ê²¼¤Î¾õÂÖ¤òɽ¤¹¿ô¤ÎϤˤʤ롣
548 .\"O \ 0\ \-\ No errors
551 .\"O \ 1\ \-\ File system errors corrected
552 \ 1\ \-\ ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¨¥é¡¼¤¬½¤Àµ¤µ¤ì¤¿
554 .\"O \ 2\ \-\ File system errors corrected, system should
556 .\"O \ \ \ \ be rebooted
558 \ 2\ \-\ ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¨¥é¡¼¤¬½¤Àµ¤µ¤ì¤¿¡£
560 \ \ \ \ ¥·¥¹¥Æ¥à¤ò¥ê¥Ö¡¼¥È¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤
562 .\"O \ 4\ \-\ File system errors left uncorrected
563 \ 4\ \-\ ¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î¥¨¥é¡¼¤¬½¤Àµ¤µ¤ì¤Ê¤¤¤Þ¤Þ
567 .\"O \ 8\ \-\ Operational error
570 .\"O \ 16\ \-\ Usage or syntax error
571 \ 16\ \-\ ÍøÍÑË¡¡¦Ê¸Ë¡¤Î¥¨¥é¡¼
573 .\"O \ 32\ \-\ E2fsck canceled by user request
574 \ 32\ \-\ e2fsck ¤¬¥æ¡¼¥¶Í×µá¤Ë¤è¤Ã¤Æ¥¥ã¥ó¥»¥ë¤µ¤ì¤¿
576 .\"O \ 128\ \-\ Shared library error
577 \ 128\ \-\ ¶¦Í¥é¥¤¥Ö¥é¥ê¥¨¥é¡¼
581 .\"O The following signals have the following effect when sent to
585 ¤ËÁ÷¤é¤ì¤ë¤È¡¢µ½Ò¤µ¤ì¤Æ¤¤¤ë¤è¤¦¤Ê¸ú²Ì¤òµÚ¤Ü¤¹¡£
588 .\"O This signal causes
590 .\"O to start displaying a completion bar. (See discussion of the
595 ¤Ïºî¶È¾õ¶·¤ÎËÀ¥°¥é¥Õ¤Îɽ¼¨¤ò»Ï¤á¤ë
597 ¥ª¥×¥·¥ç¥ó¤Îµ½Ò¤ò¸«¤è)¡£
600 .\"O This signal causes
602 .\"O to stop displaying a completion bar.
605 ¤Ïºî¶È¾õ¶·¤ÎËÀ¥°¥é¥Õ¤Îɽ¼¨¤ò¤ä¤á¤ë¡£
606 .\"O .SH REPORTING BUGS
608 .\"O Almost any piece of software will have bugs. If you manage to find a
609 .\"O filesystem which causes
611 .\"O to crash, or which
613 .\"O is unable to repair, please report it to the author.
614 ¤É¤ó¤Ê¥½¥Õ¥È¥¦¥§¥¢¤Ë¤â¥Ð¥°¤Ï¤Ä¤¤â¤Î¤Ç¤¢¤ë¡£
619 ¤Ë¤è¤Ã¤Æ½¤Éü¤Ç¤¤Ê¤¤»öÂÖ¤¬È¯À¸¤·¤¿¤ê¤·¤¿¾ì¹ç¤Ï¡¢
620 ºî¼Ô¤ËÏ¢Íí¤·¤Æ¤Û¤·¤¤¡£
622 .\"O Please include as much information as possible in your bug report.
623 .\"O Ideally, include a complete transcript of the
625 .\"O run, so I can see exactly what error messages are displayed. (Make sure
626 .\"O the messages printed by
628 .\"O are in English; if your system has been
629 .\"O configured so that
631 .\"O messages have been translated into another language, please set the the
633 .\"O environment variable to
635 .\"O so that the transcript of e2fsck's output will be useful to me.)
636 ¥Ð¥°Êó¹ð¤Ë¤Ï¤Ç¤¤ë¤À¤±Â¿¤¯¤Î¾ðÊó¤òÆþ¤ì¤Æ¤Û¤·¤¤¡£
638 ¤Î´°Á´¤Ê¼Â¹ÔµÏ¿¤¬¤¢¤ì¤Ð¡¢
639 »ä¤Ï¤É¤Î¤è¤¦¤Ê¥¨¥é¡¼¤¬È¯À¸¤·¤Æ¤¤¤ë¤«¤ò³Îǧ¤¹¤ë¤³¤È¤¬¤Ç¤¤ë¡£
641 ¤Çɽ¼¨¤µ¤ì¤ë¥á¥Ã¥»¡¼¥¸¤¬±Ñ¸ì¤Ç¤¢¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤Û¤·¤¤¡£
643 ¤Î¥á¥Ã¥»¡¼¥¸¤¬Â¾¤Î¸À¸ì¤ËËÝÌõ¤µ¤ì¤ë¤è¤¦¤Ë¥·¥¹¥Æ¥à¤¬ÀßÄꤵ¤ì¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
648 ¤ËÀßÄꤷ¤Æ¡¢e2fsck ¤Î½ÐÎϤμ¹ԵϿ¤¬»ä¤Ë¤È¤Ã¤ÆÌòΩ¤Ä¤è¤¦¤Ë¤·¤Æ¤Û¤·¤¤¡£)
650 .\"O have a writable filesystem where the transcript can be stored, the
652 .\"O program is a handy way to save the output of
655 ¼Â¹ÔµÏ¿¤ò½ñ¤¹þ¤à¤³¤È¤Î¤Ç¤¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤¬¤¢¤ë¤Ê¤é¡¢
657 ¥×¥í¥°¥é¥à¤òÍѤ¤¤ì¤Ð¡¢´Êñ¤Ë
661 .\"O It is also useful to send the output of
662 .\"O .BR dumpe2fs (8).
663 .\"O If a specific inode or inodes seems to be giving
665 .\"O trouble, try running the
667 .\"O command and send the output of the
669 .\"O command run on the relevant inode(s). If the inode is a directory, the
672 .\"O command will allow you to extract the contents of the directory inode,
673 .\"O which can sent to me after being first run through
674 .\"O .BR uuencode (1).
677 ÆÃÄê¤Î inode ¤ÎÉÔÎɤ¬
679 ¤ÎÆ°ºî¤ò¤ª¤«¤·¤¯¤·¤Æ¤¤¤ë¤è¤¦¤Ê¤é¡¢
681 ¥³¥Þ¥ó¥É¤òµ¯Æ°¤·¡¢³ºÅö¤¹¤ë inode ¤ËÂФ·¤Æ
683 ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¡¢¤½¤Î½ÐÎϤòÁ÷¤Ã¤Æ¤Û¤·¤¤¡£
684 ¤½¤Î inode ¤¬¥Ç¥£¥ì¥¯¥È¥ê¤Ç¤¢¤ë¾ì¹ç¤Ï¡¢debugfs ¤Î
686 ¥³¥Þ¥ó¥É¤òÍøÍѤ¹¤ì¤Ð¡¢¥Ç¥£¥ì¥¯¥È¥ê inode ¤ÎÆâÍƤò¼è¤ê½Ð¤¹¤³¤È¤¬¤Ç¤¤ë¡£
689 ¤Ë¤«¤±¤ì¤Ð¡¢¤½¤Î¤Þ¤Þ»ä¤ËÊó¹ð¤¹¤ë¤³¤È¤¬¤Ç¤¤ë¡£
690 .\"O The most useful data you can send to help reproduce
691 .\"O the bug is a compressed raw image dump of the filesystem, generated using
692 .\"O .BR e2image (8).
693 ¥Ð¥°¤òºÆ¸½¤¹¤ë¤¿¤á¤Ë¥æ¡¼¥¶¤¬Á÷¤ë¤³¤È¤Î¤Ç¤¤ëºÇ¤âÍÍѤʥǡ¼¥¿¤Ï¡¢
695 ¤ò»È¤Ã¤ÆÀ¸À®¤µ¤ì¤ë¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤Î°µ½Ì¤µ¤ì¤¿ raw ¥¤¥á¡¼¥¸¥À¥ó¥×¤Ç¤¢¤ë¡£
698 .\"O man page for more details.
703 .\"O Always include the full version string which
705 .\"O displays when it is run, so I know which version you are running.
706 »ä¤ËÊó¹ð¤¹¤ëºÝ¤Ë¤Ï¡¢¤É¤Î¥Ð¡¼¥¸¥ç¥ó¤Ê¤Î¤«»ä¤Ë¤ï¤«¤ë¤è¤¦¡¢
708 ¤Î¼Â¹Ô»þ¤Ëɽ¼¨¤µ¤ì¤ë¥Ð¡¼¥¸¥ç¥óʸ»úÎó¤òɬ¤ºÆþ¤ì¤Æ¤Û¤·¤¤¡£
713 .\"O was written by Theodore Ts'o <tytso@mit.edu>.
716 ¤Ï¡¢Theodore Ts'o <tytso@mit.edu> ¤Ë¤è¤Ã¤ÆºîÀ®¤µ¤ì¤¿¡£