From: Robinson Maureira Castillo <rmaureira@alumno.inacap.cl>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: "Pozsar Balazs" <pozsy@sch.bme.hu>,
"Jörg Prante" <joergprante@gmx.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHSET] 2.4.19-pre8-jp12
Date: Thu, 16 May 2002 11:08:14 -0400 (CLT) [thread overview]
Message-ID: <Pine.LNX.4.44.0205161105520.5254-100000@alumno.inacap.cl> (raw)
In-Reply-To: <20020516090505.GB954@louise.pinerecords.com>
On Thu, 16 May 2002, Tomas Szepe wrote:
> > But the worst problem for is supermount:
> > # mount -t supermount -o dev=/dev/cdrom none /mnt/cdrom
> > # ls -l /mnt/cdrom
> > ls: .: Stale NFS handle (~or something similar)
> > [...] (and it lists the file)
>
> Hmmm.. I've been seeing this problem in the latest -ac kernels too.
>
> Basically, a while after mounting the CD a ls on any subdir of the
> mount will complain about a 'stale NFS handle' and the device has
> to be remounted.
>
> T.
>
I'm getting the same with ftpfs, both in jp11 and jp12. Remounting doesn't
change a thing, it just shows me the root tree, I can cd into directories
if I know the name, but all I got is those nice 'stale NFS handle' as a
response from ls
Regards
Rob.
next prev parent reply other threads:[~2002-05-16 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 0:05 [PATCHSET] 2.4.19-pre8-jp12 Jörg Prante
2002-05-16 7:47 ` Pozsar Balazs
2002-05-16 9:05 ` Tomas Szepe
2002-05-16 9:19 ` Pozsar Balazs
2002-05-16 15:08 ` Robinson Maureira Castillo [this message]
2002-05-16 21:40 ` [PATCH 2.4.19pre8][RFC] remove-NFS-close-to-open from VFS (was Re: [PATCHSET] 2.4.19-pre8-jp12) Jörg Prante
2002-05-16 22:13 ` Alan Cox
2002-05-16 23:36 ` [PATCH] fixing supermount for > 2.4.19pre4 Jörg Prante
2002-05-17 3:04 ` [PATCH 2.4.19pre8][RFC] remove-NFS-close-to-open from VFS (was Re: [PATCHSET] 2.4.19-pre8-jp12) Tomas Szepe
2002-05-17 3:43 ` Jan Harkes
2002-05-16 18:33 ` [PATCHSET] 2.4.19-pre8-jp12 Jörg Prante
2002-05-16 19:39 ` Jörg Prante
2002-05-17 23:19 ` Greg KH
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=Pine.LNX.4.44.0205161105520.5254-100000@alumno.inacap.cl \
--to=rmaureira@alumno.inacap.cl \
--cc=joergprante@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@sch.bme.hu \
--cc=szepe@pinerecords.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).