From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: linux-kernel@vger.kernel.org
Cc: Miquel van Smoorenburg <miquels@cistron.nl>
Subject: Re: NFS-mounted, read-only /dev unusable in 2.6
Date: Wed, 04 Aug 2004 09:00:56 +0200 [thread overview]
Message-ID: <411089A8.8070104@bio.ifi.lmu.de> (raw)
In-Reply-To: <20040804064716.GA31600@traveler.cistron.net>
Miquel van Smoorenburg wrote:
> Assuming you have a way to reproduce this, to the NFS client
> maintainer - see the file MAINTAINERS in the kernel source.
Thanks! I will do so.
>
> But I just tried to reproduce this on 2.6.7-rc2 (it's what my
> workstation happens to be running) and I can't. I can mount an
> nfs-exported /dev from both 2.4 and 2.6 servers read-only and
> I can open devices on that read-only mount just fine.
It happens only when the server exports the fs read-only. When it
exports the fs rw and you mount it ro on the client, it works. But
with exporting ro, it fails.
Before I report this, I guess I should try 2.6.8-rc3 and see if it
works there.
Thanks!
cu,
Frank
--
Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17 Phone: +49 89 2180-4049
80333 Muenchen, Germany Fax: +49 89 2180-99-4049
next prev parent reply other threads:[~2004-08-04 7:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 8:09 NFS-mounted, read-only /dev unusable in 2.6 Frank Steiner
2004-08-03 14:13 ` Dick Streefland
2004-08-03 14:42 ` Frank Steiner
2004-08-03 17:28 ` L A Walsh
2004-08-04 6:27 ` Frank Steiner
2004-08-03 21:09 ` Miquel van Smoorenburg
2004-08-04 6:34 ` Frank Steiner
2004-08-04 6:47 ` Miquel van Smoorenburg
2004-08-04 7:00 ` Frank Steiner [this message]
2004-08-04 7:05 ` Neil Brown
2004-08-04 10:35 ` Frank Steiner
2004-08-04 11:02 ` Neil Brown
2004-08-05 6:30 ` Frank Steiner
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=411089A8.8070104@bio.ifi.lmu.de \
--to=fsteiner-mail@bio.ifi.lmu.de \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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.