> My suggestion: Set background_fsck="YES" in /etc/rc.conf and let
> the system boot up that way. _If_ you have a faulty disk or other
> data corruption, you'll notice this _before_ going multi-user and
> maybe making things worse. Yes, it might take some time, but it's
> time well invested in your data integrity.
>
> Alternative: Perform a "shutdown now" and go into single-user mode.
> Then unmount all your file systems, do "mount -o ro /" and then
> perform the fsck run on all file systems. It's typically adviced
> to perform file system checks on unmounted (or at least read-only
> mounted) file systems.
man fsck:
-----
Note that background fsck is limited to checking for only the
most commonly occurring file system abnormalities. Under certain
circumstances, some errors can escape background fsck. It is
recommended that you perform foreground fsck on your systems
periodically and whenever you encounter file-system-related pan-
ics.
---
So do a manual fsck to make sure there's no residual faults lurking.
Realise fsck wont start if it thinks its clean, (but might not be clean) so
Boot single user & type
fsck
or fsck -y
PS
/etc/rc.conf:
fsck_y_enable="YES" # to regularly force clean if fsck asks
# background_fsck="YES" # a trade off your decision
Cheers,
Julian
--
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
Reply below not above, cumulative like a play script, & indent with "> ".
Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable.
Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
