From: James Pearson <james-p@moving-picture.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: autofs@linux.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] Re: Busy inodes after unmount followed by Oops
Date: Fri, 21 May 2004 17:58:26 +0100 [thread overview]
Message-ID: <40AE3532.8EBA0D7B@moving-picture.com> (raw)
In-Reply-To: 1085157843.3666.75.camel@lade.trondhjem.org
Trond Myklebust wrote:
>
> På fr , 21/05/2004 klokka 11:44, skreiv James Pearson:
>
> > We've been running this patch on over 400 machines for the last 10 or so
> > days, and have not seen any instance of this 'VFS: Busy inodes after
> > unmount/Oops' problem above - previously, we would have seen a
> > significant number of these in the same time scale (and we are still
> > seeing the problem on machines not using the patch).
>
> Note that Greg's patch for solving the NFS client issues that were
> revealed by this bug is in 2.4.26 (and in 2.6.5)...
Not quite sure what you mean by this - I had tried Greg's patch
(http://marc.theaimsgroup.com/?l=linux-nfs&m=107604754127538&w=2)
previously - but it made no difference in my case. The kernel I'm using
now has both Greg's patch and Ian's recent autofs4 patch.
James Pearson
next prev parent reply other threads:[~2004-05-21 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 11:06 Busy inodes after unmount followed by Oops James Pearson
2004-01-09 19:13 ` [NFS] " Ian Kent
2004-05-21 15:44 ` James Pearson
2004-05-21 16:44 ` Trond Myklebust
2004-05-21 16:44 ` Trond Myklebust
2004-05-21 16:58 ` James Pearson [this message]
2004-05-22 13:04 ` [NFS] " Greg Banks
2004-05-22 15:15 ` raven
2004-05-22 15:24 ` raven
2004-05-24 15:51 ` James Pearson
2004-05-22 3:41 ` raven
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=40AE3532.8EBA0D7B@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=autofs@linux.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.