From: "Jörg Prante" <joergprante@gmx.de>
To: Pozsar Balazs <pozsy@sch.bme.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET] 2.4.19-pre8-jp12
Date: Thu, 16 May 2002 21:39:14 +0200 [thread overview]
Message-ID: <200205161941.AWE93399@netmail.netcologne.de> (raw)
In-Reply-To: <Pine.GSO.4.30.0205160941040.956-100000@balu>
> 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)
>
> But:
> # cd /mnt/cdrom
> # ls -l
> ls: .: Stale NFS handle
> # (and it doesn't even list the files)
Hi Pozsar, this is a known supermount bug. I got this as well. Supermount is
a patch for 2.4.18pre8 kernel, not for 2.4.19preX. See also
http://www.mandrake.com/en/archives/cooker/2002-04/msg00086.php
I will try my best to figure out what is happening. The open(".",...) call to
supermount returns -1 and this gives "stale NFS handle", but
open("/mnt/cdrom", ...) gives "3" or a positive number. I think the text of
the message is misleading, it has nothing to do with NFS.
Jörg
next prev parent reply other threads:[~2002-05-16 19:41 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
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 [this message]
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=200205161941.AWE93399@netmail.netcologne.de \
--to=joergprante@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@sch.bme.hu \
/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).