Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 May 2001 00:40:39 -0700 (PDT)
From:      Kirk McKusick <mckusick@FreeBSD.org>
To:        cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   cvs commit: src/etc rc
Message-ID:  <200105110740.f4B7ee040787@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
mckusick    2001/05/11 00:40:39 PDT

  Modified files:
    etc                  rc 
  Log:
  Update the fsck command in /etc/rc to use the new background
  fsck checking. Applying these changes (typically via mergemaster)
  will cause your system to start running background checks on all
  your soft update enabled filesystems (provided that you have
  a kernel with the required functionality, e.g., one built since
  the end of April). Please report any and all problems to
  mckusick@mckusick.com (not mckusick@freebsd.org which I read
  infrequently). See the comment above the fsck command in /etc/rc
  for instructions on how to disable background checking should it
  cause you too much trouble.
  
  Several FAQs:
  
  1) Can I reboot before the background checks are done?
  
  Ans) Yes, when the system restarts the checks will pick up
       where they left off.
  
  2) Can a crash during checking corrupt my filesystem?
  
  Ans) No, recovered resources are returned to the system using soft
       updates which ensure that the freeing is done in a safe order.
  
  3) How will I know if any background checks are being done?
  
  Ans) Filesystems that are to be checked in background will be listed
       as `DEFER FOR BACKGROUND CHECKING' at the usual fsck check time
       during system startup.
  
  4) What happens to the output of the background checks?
  
  Ans) It is sent to syslog `daemon' facility log level `notice'.
  
  5) When will this feature be available in the 4.X kernel?
  
  Ans) Never. It is much too radical and extensive a change to be
       MFC'ed. Besides, it needs many months of experience and
       tuning before it is ready for widespread use.
  
  6) What happens if a background fsck fails (i.e., fsck finds
     errors that would normally require a manual fsck)?
  
  Ans) The filesystem will be marked as needing a manual fsck.
       At the next system reboot, the check will be done in
       foreground and the usual actions taken (usually a failure
       to go multi-user until fsck has been run by hand on the
       affected filesystem).
  
  Revision  Changes    Path
  1.263     +8 -2      src/etc/rc


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105110740.f4B7ee040787>