From: Wendy Cheng <wcheng@redhat.com>
To: nfs@lists.sourceforge.net
Subject: Re: query about kernel 2.4.21-37.ELsmp
Date: Thu, 08 Jun 2006 09:50:54 -0400 [thread overview]
Message-ID: <44882B3E.9000008@redhat.com> (raw)
In-Reply-To: <20060608085004.73262.qmail@web51611.mail.yahoo.com>
mehta kiran wrote:
>I tried all the steps you talked
>about mount remains busy. The only
>thing effective which you mentioned
>is killing nfsd. This causes kernel to
>release all reference to exported fs.
>
>Steps to reproduce this problem :
>
>1. mount <device> <mountpoint>
>2. export it
>3. unexport it
>4. try umounting it. it wont
>
>
>
>
>
I don't seem to be able to create it ..... ok, two more things:
* nfs-utils updated ?
* do a "cat /proc/fs/nfs/exports" when umount fails and passes back the
info.
* give me the "exact" command you used for unexport.
-- Wendy
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-06-08 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 4:24 query about kernel 2.4.21-37.ELsmp mehta kiran
2006-06-08 6:35 ` Wendy Cheng
2006-06-08 6:39 ` Wendy Cheng
2006-06-08 8:50 ` mehta kiran
2006-06-08 13:50 ` Wendy Cheng [this message]
2006-07-02 15:11 ` Jeff Layton
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=44882B3E.9000008@redhat.com \
--to=wcheng@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox