File:  [MW Coherent from dump] / coherent / a / usr / man / COHERENT / fsck
Revision 1.1.1.1 (vendor branch): download - view: text, annotated - select for diffs
Wed May 29 04:56:34 2019 UTC (7 years ago) by root
Branches: MarkWilliams, MAIN
CVS tags: relic, HEAD
coherent



fsck                         Command                         fsck




Check and repair file systems interactively

/eettcc/ffsscckk [ -ffnnqqyy ] [ -tt _t_e_m_p_f_i_l_e ] [ _f_i_l_e_s_y_s_t_e_m ... ]

fsck checks  and interactively repairs  file systems.  If  all is
well, ffsscckk merely prints the  number of files used, the number of
blocks used, and the number of blocks that are free.  If the file
system is found to be inconsistent in one of the aspects outlined
below,  ffsscckk asks  whether it  should  fix the  inconsistency and
waits for you to reply yyeess or nnoo.

The following file  system aspects are checked for consistency by
fsck:

*  If  a block is claimed  by more than one  i-node, by an i-node
   and the free list, or more than once in the free list.

*  Whether  an i-node or  the free list claims  blocks beyond the
   file system's range.

*  Link counts that are incorrect.

*  Whether the directory size is not aligned for 16 bytes.

*  Whether the i-node format is correct.

*  Whether any blocks are not accounted for.

*  Whether a file points to an unallocated i-node.

*  Whether a file's i-node number is out of range.

*  Whether the super block refers to more than 65,536 i-nodes.

*  Whether  the super block  assigned more blocks  to the i-nodes
   than the system contains.

*  Whether the format of the free block list is correct.

*  Whether  the counts of the  total free blocks and  the free i-
   nodes are correct.

fsck prints  a warning message when  a file name is  null, has an
embedded slash  `/', is not null-padded, or if  `.' or `..' files
do not have the correct i-node numbers.

When ffsscckk repairs a file  system, any file that is orphaned (that
is, allocated  but not referenced) is deleted if  it is empty, or
copied to  a directory called lloosstt+ffoouunndd,  with its i-node number
as its name.  The directory  lloosstt+ffoouunndd must exist in the root of
the file  system being  checked before  ffsscckk is executed,  and it
must have room for  new entries without requiring that new blocks
be allocated.



COHERENT Lexicon                                           Page 1




fsck                         Command                         fsck



fsck accepts the following options:

-ff Fast check.  ffsscckk only checks whether a block has been claimed
   by more  than one i-node, by  an i-node and the  free list, or
   more  than once  in the  free list.   If necessary,  ffsscckk will
   reconstruct the free list.

-nn No  option: a default  reply of nnoo  is given to  all of ffsscckk's
   questions.

-qq Quiet option: run quietly.  ffsscckk automatically removes all un-
   referenced pipes,  and automatically fixes list  counts in the
   super block and the free list.  File-name warning messages are
   suppressed, but  ffsscckk still prints  the number of  files used,
   the  number of  blocks  used, and  the number  of blocks  that
   remain free.

-tt Specify temporary file option: ffsscckk uses RAM device /ddeevv/rrrraamm11
   for  temporary storage when  checking filesystems  larger than
   approximately 35  megabytes.  This  option allows the  user to
   specify temporary storage other than the RAM device.

-yy Yes option:  a default reply of yyeess is  given to all of ffsscckk's
   questions.

If you  do not name  a file system  in ffsscckk's command  line, ffsscckk
checks the file systems named in the file /eettcc/cchheecckklliisstt.

If fsck is invoked for a file system larger than approximately 35
megabytes,  it  uses  the  RAM  device /dev/rram1  for  temporary
storage.  For  this reason, it  is strongly advised  that you not
use /dev/rram1 as a RAM disk.

***** Files *****

/eettcc/cchheecckklliisstt

***** See Also *****

clri, commands, icheck, ncheck, ram, sync, umount

***** Notes *****

The  correction  of  file  systems  almost  always  involves  the
destruction of data.

You can run fsck only  when the COHERENT system is in single-user
mode.

Previous editions of fsck could check no partition larger than 35
megabytes.  This restriction has been lifted.






COHERENT Lexicon                                           Page 2



unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.