Re: more on fsck with securelevel

From: Bill Moran (wmoran_at_potentialtech.com)
Date: 06/05/04

  • Next message: TEC Meganet: "Re: more on fsck with securelevel"
    Date: Fri, 4 Jun 2004 19:35:47 -0400
    To: Brooks Davis <brooks@one-eyed-alien.net>
    
    

    Brooks Davis <brooks@one-eyed-alien.net> wrote:

    > On Fri, Jun 04, 2004 at 05:05:34PM -0500, J.D. Bronson wrote:
    > > I did set this in /etc/rc.conf:
    > > fsck_y_enable="YES"
    > >
    > > But I was wondering if this might be a good idea too:
    > > (looking at the defaults)
    > >
    > > fsck_y_enable="NO" # Set to YES to do fsck -y if the initial preen
    > > fails.
    > > background_fsck="YES" # Attempt to run fsck in the background where
    > > possible.
    > > background_fsck_delay="60" # Time to wait (seconds) before starting the
    > > fsck.
    > >
    > > ..might it not be prudent to set 'background_fsck="NO"' when running in
    > > secure mode?
    > >
    > > Eventhough I shut down carefully, sometimes it still feels the need to run
    > > fsck (even with soft updates)...but when running securelevel, is it
    > > actually going to accomplish anything?
    >
    > I think just setting background_fsck_delay=0 may allow bgfsck to work.
    > Once fsck has opened the FS, I think it should keep it open and writes
    > should work. I'm not 100% sure of that though.

    fsck_y_enable determines what happens when a normal fsck fails. If it's set
    to "NO", you're dumped into single-user mode with a scary message. If it's
    set to "YES", then fsck is rerun with the -y option. Setting it to "YES" will
    allow the system to boot automatically under almost all conditions, but you may
    lose data that you could have recovered if you'd run fsck manually ... assuming
    you know what you're doing well enough to recover that data.

    background_fsck controls whether the initial boot fsck is run in the background,
    after booting, or in the foreground during the boot, forcing the boot process
    to wait on it (background_fsck="NO" is basically the same behaviour as pre-5
    systems)

    background_fsck_delay is pretty obvious.

    Hopefully, that will help you reach a config that works for you.

    -- 
    Bill Moran
    Potential Technologies
    http://www.potentialtech.com
    _______________________________________________
    freebsd-performance@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-performance
    To unsubscribe, send any mail to "freebsd-performance-unsubscribe@freebsd.org"
    

  • Next message: TEC Meganet: "Re: more on fsck with securelevel"

    Relevant Pages

    • Re: fsckd - FIXED
      ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
      (Debian-User)
    • SUMMARY: Cant boot X1 - fsck problem?!?
      ... Then next step was to find alternate superblock and run fsck against that ... After this I was able to boot up my Solaris 2.8 and everything is working ... Entering System Maintenance Mode ... mount: the state of /dev/dsk/c0t0d0s0 is not okay ...
      (SunManagers)
    • fstab entries for external USB hard drives led to fsck.ext3 failure on boot, bug?
      ... 'F!3@$%ing fsck! ... Please repair the file system manually. ... CONTROL-D will terminate this shell and resume system boot. ... were to allow me to quickly mount an external hard drive ...
      (Debian-User)
    • Re: fsckd
      ... filesystem errors on boot, with the "hit control-D to continue or give root ... to fix the errors with fsck. ... filesystem and inability to reboot. ...
      (Debian-User)
    • Re: [SLE] fsck!!!
      ... > A little informed but still desperate to fsck the system. ... How to get to the CLI from the rescue option when booting off the ... Continue to boot to the rescue system. ... kernel versions and sources required if you move your harddrive to another ...
      (SuSE)