All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Liontooth <liontooth@cogweb.net>
To: Neil Brown <neilb@suse.de>
Cc: 443591@bugs.debian.org, nfs@lists.sourceforge.net
Subject: Re: Bug#443591: nfs-kernel-server: Unexporting directories no	longer working
Date: Mon, 24 Sep 2007 16:29:02 -0700	[thread overview]
Message-ID: <46F8483E.3000103@cogweb.net> (raw)
In-Reply-To: <18167.24613.796605.199161@notabene.brown>


Hi Neil,

Thanks for looking.

Neil Brown wrote:
> On Sunday September 23, sgunderson@bigfoot.com wrote:
>   
>> On Sat, Sep 22, 2007 at 10:42:31AM -0700, David Liontooth wrote:
>>     
>>> Package: nfs-kernel-server
>>> Version: 1:1.1.0-13
>>> Severity: normal
>>>
>>>
>>> The command to unexport a directory appears to no longer have any effect.
>>>
>>> I issue "exportfs -u :/tv01" and "exportfs" shows /tv01 still exported; consequently, I cannot unmount it.
>>> In contrast, removing /tv01 from /etc/exports and then running exportfs -ra successfully removes the export.
>>>
>>> This used to work fine.
>>>       
>> Sending this on to upstream, as I cannot see any good reason offhand why it
>> should not work.
>>     
>
> Some simple testing and code review suggests that this works as
> expected.  However it is possible that I am expecting something
> different to you, or testing something different.
>
> You say you:
>     exportfs -u :/tv01
>
> What exactly is in your /etc/exports that this is expected to revert?
>   

/tv01 \
        134.32.443.30(ro,no_subtree_check,async) \
        134.32.443.32(ro,no_subtree_check,async) \
        134.32.443.33(ro,no_subtree_check,async) \
        134.32.443.34(ro,no_subtree_check,async) \
        134.32.443.35(ro,no_subtree_check,async) \
        134.32.443.36(ro,no_subtree_check,async) \
        134.32.443.37(ro,no_subtree_check,async)

Several other drives have similar entries.
> The obvious answer would be
>
>     /tv01  (some,flags,here)
>
> however "exportfs" will complain about that, so I suspect not.
>
> Maybe you have:
>
>     /tv01 somehost(someflags)  otherhost(otherflags)
>
> and you expect
>     exportfs -u :/tv01
>
> to unexport /tv01 to all hosts?  I would agree that doesn't work.  Did
> it ever?  What version?
>   

I see. So that would unexport only the first one?

Can I unexport only /tv01 to all hosts?
(If it's just a matter of my being uninformed, let's close the bug --
but I'd appreciate an answer!)

> As an aside, you can always:
>    exportfs -f
> and then unmount filesystems.  They will be free to be unmounted until
> the next NFS access request arrives.  Maybe that will serve your
> needs?
>   
I see -- that may be helpful -- but what if someone is accessing one of
the drives right then?
I would prefer to have individual control; I export a dozen other drives
to several different machines, and they should not be unexported.

Dave





-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-09-24 23:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070922174231.11200.29119.reportbug@localhost.localdomain>
2007-09-23  0:01 ` Bug#443591: nfs-kernel-server: Unexporting directories no longer working Steinar H. Gunderson
2007-09-24  6:58   ` Neil Brown
2007-09-24 23:29     ` David Liontooth [this message]
2007-10-12 19:59       ` Bug#443591: " Steinar H. Gunderson
2007-10-24  0:09         ` David Liontooth
2007-10-15  0:02       ` Neil Brown

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=46F8483E.3000103@cogweb.net \
    --to=liontooth@cogweb.net \
    --cc=443591@bugs.debian.org \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /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.