Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!decwrl!ucbvax!bloom-beacon!eru!luth!sunic!mcsun!hp4nl!dutrun!tncsatr From: tncsatr@dutrun.UUCP (Arthur van der Harg) Newsgroups: comp.sys.hp Subject: Re: /etc/umount under HP-UX 7.0 on 9k/835 Summary: did you use a *soft* mount Message-ID: <1865@dutrun.UUCP> Date: 16 Aug 90 14:00:20 GMT References: Reply-To: tncsatr@dutrun.UUCP (A.J.M. v.d. Harg) Organization: Delft University of Technology, The Netherlands Lines: 29 In article schell@hazel.ucdavis.edu (Stephan Schell) writes: [...] |crashed, become severely loaded, started to thrash). In such situations, |/etc/umount refuses to unmount the file system in question. One |person suggested using /etc/umount -f to "force" the umount operation, |but this is clearly preposterous since umount (under HP-UX 7.0 on |9000/835) does not recognize this option. The only fix seems to be to |reboot the machine. THIS IS LUDICROUS. If I can ungracefully terminate |my relationship with an NFS server via a reboot, why shouldn't I be able |to accomplish the same thing using umount and avoid the reboot (which |tends to greatly disrupt other users)? | If I understand the problem well, the solution might be to specify 'soft' mounting when you mount the system. I gathered that in those cases your own machine wqould not be dependent on the (mal-)functioning of the 'home' machine of the file system. I expect (disclaimer: I am not completely sure) that in this case you can umount the system without waiting for a confirmation from the other machine. I think that the confirmation is the problem when the other machine goes down. Hope this helps! |Stephan Schell schell@llandru.ucdavis.edu -- /* The use of 'goto' statements is discouraged, especially with the label HELL: Arthur van der Harg (arthur@dutfdsa.tudelft.nl) */