Linux NFS development
 help / color / mirror / Atom feed
From: "Nicholas Lafferty" <nlafferty@pennswoods.net>
To: "Neil Brown" <neilb@cse.unsw.edu.au>
Cc: "nfs" <nfs@lists.sourceforge.net>
Subject: Re: Can't mount nfs rw
Date: Fri, 6 Sep 2002 10:45:11 -0400	[thread overview]
Message-ID: <000b01c255b4$016cb190$9300a8c0@gridlock> (raw)
In-Reply-To: 15735.62892.38035.663384@notabene.cse.unsw.edu.au

Unfortunaly they are on the same filesystem. I'm mounting / as /ro on the
client and symlinking to the need directories. I changed / to export as rw
and then I remount / onto /ro as ro after the system boots. Does that sound
like a safe workaround?

Thanks,
Nick

----- Original Message -----
From: "Neil Brown" <neilb@cse.unsw.edu.au>
To: "Nicholas Lafferty" <nlafferty@pennswoods.net>
Cc: "nfs" <nfs@lists.sourceforge.net>
Sent: Thursday, September 05, 2002 8:24 PM
Subject: Re: [NFS] Can't mount nfs rw


> On Thursday September 5, nlafferty@pennswoods.net wrote:
> > I'm not quite sure I know your perlf00. What does :   perl -i -p -e
> > 's,192.168.0.0\(,192.168.0.0/255.255.255.0\(,' /etc/exports  actually
do? I
> > issue the command and it just hangs. Does it change my exports file in
some
> > way?
>
> Hmmm. The command worked for me.
> It uses perl to do an in-place (-i) edit of /etc/exports which
> changes every
>    192.160.0.0(
> to
>    192.160.0.0/255.255.255.0(
>
> Producing
> / 192.168.0.0/255.255.255.0(ro,no_root_squash)
> /home/guest/share       192.168.0.0/255.255.255.0(ro,no_root,squash)
> /home/guest/01            192.168.0.0/255.255.255.0(rw,no_root_squash)
> /home/guest/02            192.168.0.0/255.255.255.0(rw,no_root_squash)
> /home/guest/03            192.168.0.0/255.255.255.0(rw,no_root_squash)
>
>
> As it was, the only filesystem that was exported to 192.168.*.* was /,
> and it was exported read-only, just as you reported.
>
> Note: this will only work if /home/guest/* are on a different
> filesystem to /.  If they are on the same filesystem, you may as well
> just export '/' rw.
>
> NeilBrown
>
> >
> > Thanks,
> >
> > Nick
> >
> > ----- Original Message -----
> > From: "Neil Brown" <neilb@cse.unsw.edu.au>
> > To: "Nicholas Lafferty" <nlafferty@pennswoods.net>
> > Cc: "nfs" <nfs@lists.sourceforge.net>
> > Sent: Wednesday, September 04, 2002 10:34 PM
> > Subject: Re: [NFS] Can't mount nfs rw
> >
> >
> > > On Wednesday September 4, nlafferty@pennswoods.net wrote:
> > > > I'm having problems getting my diskless clients to mount NFS
directories
> > in
> > > > Read-Write mode. I'm using bpbatch and tftp to transfer the kernel
and a
> > > > ramdisk for the root file system. I pass an initscript to the kernel
> > that
> > > > mounts the root file system of the server as read-only (mounts on
/ro),
> > > > /home/guest/share mounts as ro2 (read-only), and /home/guest/01
mounts
> > as
> > > > /rw (read-write). Then init is invoked. The problem is that all of
the
> > > > mounts are read-only.
> > > >
> > > > #Here is what my initscript does for the mounts.
> > > > mount-t nfs -o nolock,ro,vers=2 $SERVER:/      /ro
> > > > mount-t nfs -o nolock,ro,vers=2 $SERVER:/home/guest/share      /ro2
> > > > mount-t nfs -o nolock,rw,vers=2 $SERVER:/home/guest/$ID      /rw
> > > >
> > > > /sbin/init '#'
> > > >
> > > > # Here is my /etc/exports
> > > > /
> > > > 192.168.0.0/255.255.255.0(ro,no_root_squash)
> > > > /home/guest/share       192.168.0.0(ro,no_root,squash)
> > > > /home/guest/01            192.168.0.0(rw,no_root_squash)
> > > > /home/guest/02            192.168.0.0(rw,no_root_squash)
> > > > /home/guest/03            192.168.0.0(rw,no_root_squash)
> > > >
> > > > Any suggestions on some other things to try?
> > > >
> > >
> > >
> > > perl -i -p -e 's,192.168.0.0\(,192.168.0.0/255.255.255.0\(,'
/etc/exports
> > >
> > > NeilBrown
> > >
> > >
> > > -------------------------------------------------------
> > > This sf.net email is sponsored by: OSDN - Tired of that same old
> > > cell phone?  Get a new here for FREE!
> > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> > > _______________________________________________
> > > NFS maillist  -  NFS@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/nfs
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> NFS maillist  -  NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs



-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2002-09-06 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 17:39 Can't mount nfs rw Nicholas Lafferty
2002-09-05  2:34 ` Neil Brown
2002-09-05 14:46   ` Nicholas Lafferty
2002-09-06  0:24     ` Neil Brown
2002-09-06 14:45       ` Nicholas Lafferty [this message]

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='000b01c255b4$016cb190$9300a8c0@gridlock' \
    --to=nlafferty@pennswoods.net \
    --cc=neilb@cse.unsw.edu.au \
    --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