hi gerald,
on redhat systems there is a file you can edit to put in fsck parameters, there might 
be
on your mandrake, havent had time to look at the mandrakes at home.

look at the file /etc/rc.d/rc.sysinit
there is a stanza that says:

if [ -f /fsckoptions ]; then
        fsckoptions=`cat /fsckoptions`
    else
        fsckoptions=
fi

when your machine reboots it reads this rc.sysinit file and when it sees the 
"/fsckoptions" it then
runs fsck with the options contained within.

depending on your flavor of unix you either need to add a -Y or -a to that file.

word of caution: some people dont like to autofsck becuase of the potential data loss
they MAY result, you've better have a backup protocol in place to save your data.

hope this helps,
---lem



Gerald Timothy Quimpo wrote:

> hello all,
>
> i've got a Mandrake 8.2 box (i will eventually upgrade to 9.0, so version is
> not the problem).  i have it running at a remote location in the philippines.
> there are occasional sudden power glitches (sudden power drop, or brownout
> for a few seconds, minutes or hours, etc).  all filesystems are ext2.
>
> i've had problems with some filesystems requiring a manual fsck upon
> reboot (mainly the one that has /var on it, but also some other partitions
> that are particularly active).  the people onsite are not linux savvy and
> it's unlikely that they ever will be, even after training : lack of
> incentive).  so having them type the root password and then do a manual
> fsck on the device is not likely to work right.
>
> what's the best way to handle this?  i'd like to completely avoid the
> fsck.  i realize that using one of the journalled filesystems should either
> help a lot or completely fix the problem.  on the other hand, i've had
> problems (major data loss and occasional weirdness, inability to
> delete directories or files, etc) when journalled filesystems (actually,
> only reiser, have not tested with ext3 or xfs)  would safely get through
> the reboot but then some files or directories would be inaccessible
> unless a manual fsck was done (requiring yet another reboot).
>
> what do people find is the best solution that provides stability despite
> sudden power loss?  i used to do update -s 1 in inittab.  that worked
> for a while.  but maybe that was because i was there to do the fsck
> when the box wouldn't reboot.  it hasn't been working since i've been
> away though, so maybe it was a fluke or an accident having to do with
> my being around to fix things manually then.
>
> personally, i favor reiserfs.  but i'm not too happy with its robustness
> in the face of sudden and random power loss (i.e., me turning off
> the power button without shutting down).  what filesystem types and
> particular practices are recommended for boxes that are going to shut
> down randomly a lot?
>
> tiger
>
> --
> Gerald Timothy Quimpo  tiger*quimpo*org gquimpo*sni-inc.com tiger*sni*ph
> Public Key: "gpg --keyserver pgp.mit.edu --recv-keys 672F4C78"
>                    Veritas liberabit vos.
>
> _
> Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
> To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
>
> Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph
>
> To subscribe to the Linux Newbies' List: send "subscribe" in the body to 
>[EMAIL PROTECTED]

--
======== [DISCLAIMER] ========
This communication is intended for the addressee(s) and may contain confidential and 
legally privileged information.
We do not waive confidentiality or privilege by mistransmission.  If you have received 
this communication in error,
any use, dissemination, printing or copying is strictly prohibited; please destroy all 
electronic and paper copies and
notify the sender immediately.
======== [/DISCLAIMER] ========


_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]

Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph

To subscribe to the Linux Newbies' List: send "subscribe" in the body to 
[EMAIL PROTECTED]

Reply via email to