All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Mcdermott <smcdermott@questra.com>
To: "Cole, Timothy D." <tdcole@northropgrumman.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Re: Broken umount -f
Date: Thu, 16 Jan 2003 14:56:33 -0500	[thread overview]
Message-ID: <20030116195633.GE3473@questra.com> (raw)
In-Reply-To: <7F21D7A9E7D9D51192CB0002A53F93C73C28EA@xcgmd024.md.essd.northgrum.com>

Cole, Timothy D. on Thu 16/01 11:45 -0800:
> > But, I still think that with `intr', umount -f should work.
> 
> Agreed on that count -- I didn't really mean to suggest otherwise.

I meant, that with `nointr' it should work.  I made a couple of typos in
that email :)

> Unmounting is orthagonal to signal delivery, so really intr/nointr
> shouldn't influence umount -f's behavior.

as it is now, with `nointr' the signals aren't delivered when there is
pending IO, apparently (don't know if that's what really happens in the
kernel)

> > btw the NFS HOWTO recommends hard,nointr
> 
> I think there was a typo in an some earlier versions -- the current
> version of the NFS HOWTO
> (http://nfs.sourceforge.net/nfs-howto/client.html) recommends
> hard,intr.

I think I read it wrong.  I seem to have dyslexia or something...

anyways thanks to all for this useful discussion, I have remounted my
systems with intr and that solution is good enough for now.


-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache 
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-01-16 19:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 19:45 Re: Broken umount -f Cole, Timothy D.
2003-01-16 19:56 ` Scott Mcdermott [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-15 19:59 Heflin, Roger A.
2003-01-16  3:37 ` Scott Mcdermott
2003-01-15 18:46 Re: broken " Cole, Timothy D.
2003-01-15 17:04 Lever, Charles
2003-01-15 17:23 ` Scott Mcdermott
     [not found] ` <20030115130759.B11894@ti19>
2003-01-15 18:22   ` Bill Rugolsky Jr.
2003-01-15 18:24   ` Scott Mcdermott
2003-01-16 20:49 ` Ion Badulescu
2003-01-15 15:35 Murata, Dennis W (SAIC)
2003-01-15 14:45 Lever, Charles
2003-01-15 16:32 ` Scott Mcdermott
2003-01-14 19:49 Cole, Timothy D.
2003-01-14 19:36 Lever, Charles
2003-01-15  5:19 ` Scott Mcdermott
2003-01-15  5:21   ` Scott Mcdermott
2003-01-14 19:30 Cole, Timothy D.
2003-01-14 15:56 [NFS] " Lever, Charles
2003-01-14 17:07 ` Scott Mcdermott
2003-01-14 19:06   ` Trond Myklebust
2003-01-14 19:19     ` Scott Mcdermott
2003-01-14 19:32       ` Brian Tinsley
2003-01-14 19:35       ` Trond Myklebust
2003-01-14 22:17         ` Scott Mcdermott
2003-01-14 22:29           ` Steven N. Hirsch
2003-01-14 22:27         ` Steven N. Hirsch
2003-01-14 19:39     ` Benjamin LaHaise
2003-01-14 19:52       ` Trond Myklebust
2003-01-14 19:56         ` Benjamin LaHaise

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030116195633.GE3473@questra.com \
    --to=smcdermott@questra.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=tdcole@northropgrumman.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.