Hi,
I am using softdog in my application. One of the problems I am facing is,
when the system comes up after the reboot forced by softdog, file system gets
corrupted and fsck has to check. Some times fsck fails to force check the file
system and
the system enters in to run level 1, leading to manual intervention.
Any idea how to unmount the file system before the system is rebooted by
softdog, so
that system always comes up properly without manual intervention.
Thanks
-Girish
"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain privileged or confidential information and should
not be circulated or used for any purpose other than for what it is intended. If
you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that you
are strictly prohibited from using, copying, altering, or disclosing the
contents of this message. HSS accepts no responsibility for loss or damage
arising from the use of the information transmitted by this email including
damage from virus."
In article <[email protected]> you wrote:
>
>
> Hi,
> I am using softdog in my application. One of the problems I am facing is,
> when the system comes up after the reboot forced by softdog, file system gets
> corrupted and fsck has to check. Some times fsck fails to force check the file
> system and
> the system enters in to run level 1, leading to manual intervention.
>
> Any idea how to unmount the file system before the system is rebooted by
> softdog, so
> that system always comes up properly without manual intervention.
Bad idea. The point in using a watchdog is that you want to *reliably*
reboot your failed machine. What if your umount hangs for some reason?
(I've seen this...)
Use a journalling filesystem instead.
Juri
--
Juri Haberland <[email protected]>
> I am using softdog in my application. One of the problems I am facing is,
> when the system comes up after the reboot forced by softdog, file system gets
> corrupted and fsck has to check. Some times fsck fails to force check the file
> system and
> the system enters in to run level 1, leading to manual intervention.
Convert the file system to ext3 and use ext3, then you will get a few second
pause on the journal playback and the machine will return without an fsck
being needed