mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* file system unmount
@ 2002-01-23 11:13 gspujar
  2002-01-23 11:21 ` Juri Haberland
  2002-01-27 19:55 ` Alan Cox
  0 siblings, 2 replies; 5+ messages in thread
From: gspujar @ 2002-01-23 11:13 UTC (permalink / raw)
  To: linux-kernel



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."






^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: file system unmount
  2002-01-23 11:13 file system unmount gspujar
@ 2002-01-23 11:21 ` Juri Haberland
  2002-01-27 19:55 ` Alan Cox
  1 sibling, 0 replies; 5+ messages in thread
From: Juri Haberland @ 2002-01-23 11:21 UTC (permalink / raw)
  To: gspujar; +Cc: linux-kernel

In article <65256B4A.003D4CD1.00@sandesh.hss.hns.com> 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  <juri@koschikode.com> 


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: file system unmount
  2002-01-23 11:13 file system unmount gspujar
  2002-01-23 11:21 ` Juri Haberland
@ 2002-01-27 19:55 ` Alan Cox
  1 sibling, 0 replies; 5+ messages in thread
From: Alan Cox @ 2002-01-27 19:55 UTC (permalink / raw)
  To: gspujar; +Cc: linux-kernel

> 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: file system unmount
  2002-01-23  6:08 gspujar
@ 2002-01-23 17:03 ` Andreas Dilger
  0 siblings, 0 replies; 5+ messages in thread
From: Andreas Dilger @ 2002-01-23 17:03 UTC (permalink / raw)
  To: gspujar; +Cc: linux-kernel, achowdhry

On Jan 23, 2002  11:38 +0530, gspujar@hss.hns.com wrote:
> 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.

That is like asking for advance notice of system failures -> can't be done.

What you really want is a journaled filesystem (e.g. ext3 or resierfs)
which avoids the lengthy/troublesome fsck stage.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


^ permalink raw reply	[flat|nested] 5+ messages in thread

* file system unmount
@ 2002-01-23  6:08 gspujar
  2002-01-23 17:03 ` Andreas Dilger
  0 siblings, 1 reply; 5+ messages in thread
From: gspujar @ 2002-01-23  6:08 UTC (permalink / raw)
  To: linux-kernel; +Cc: achowdhry




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 Systmes 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 transimitted by this email including
damage from virus."






^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2002-01-27 19:42 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-01-23 11:13 file system unmount gspujar
2002-01-23 11:21 ` Juri Haberland
2002-01-27 19:55 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-01-23  6:08 gspujar
2002-01-23 17:03 ` Andreas Dilger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®