All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dean S. Messing" <deanm@sharplabs.com>
To: nfs@lists.sourceforge.net
Subject: Re: Help: nfs not able to mount large (loopback) directory
Date: Sat,  4 Jun 2005 23:07:08 -0700 (PDT)	[thread overview]
Message-ID: <20050605060708.A7FF4112D0@pons> (raw)
In-Reply-To: <1117862910.19354.172.camel@seki.nac.uci.edu> (message from Dan Stromberg on Fri, 03 Jun 2005 22:28:30 -0700)



On Fri, 2005-06-03 at 20:19 -0700, Dean S. Messing wrote:

: > I have a large .iso image (4GB) on machine B which I have loopback
: > mounted to directory /mnt/disk.
: > When I try to nfs mount B:/mnt/disk to machine A I get a "permission
: > denied" error.
: > If I replace the 4GB image on machine B with, say, a 700MB .iso image,
: > I have no problem with the NFS mount on machine A.
: > I'm running the latest version of MandrivaLinux (2005LE == Mandrake 10.2)
: > on machine B and MandrakeLinux 10.0 on machine A so the nfs utilites
: > on machine B (the server) should be nearly current.
: > In fact:
: >
: > [root@neuron ~]# rpcinfo -p
: >    program vers proto   port
: >     100000    2   tcp    111  portmapper
: >     100000    2   udp    111  portmapper
: >     100003    2   udp   2049  nfs
: >     100003    3   udp   2049  nfs
: >     100003    4   udp   2049  nfs
: >     100003    2   tcp   2049  nfs
: >     100003    3   tcp   2049  nfs
: >     100003    4   tcp   2049  nfs
: >     100021    1   udp  34593  nlockmgr
: >     100021    3   udp  34593  nlockmgr
: >     100021    4   udp  34593  nlockmgr
: >     100021    1   tcp  33635  nlockmgr
: >     100021    3   tcp  33635  nlockmgr
: >     100021    4   tcp  33635  nlockmgr
: >     100005    1   udp    846  mountd
: >     100005    1   tcp    849  mountd
: >     100005    2   udp    846  mountd
: >     100005    2   tcp    849  mountd
: >     100005    3   udp    846  mountd
: >     100005    3   tcp    849  mountd
: >     100024    1   udp    888  status
: >     100024    1   tcp    891  status
: >
: > Is it the case that nfs (mountd?) can't handle "large" files?
: > Any help will be much appreciated.
: 
: I also have found that even small ISO images will lead to problems if
: you loopback mount them and NFS export them - EG via NFS v3.
: 
: However, if I loopback mount the ISO image, copy it to an ext3 directory
: with a tar | tar pipeline, and then NFS export that ext3 directory in
: the same way, things work fine.
: 
: I'm finding that often userspace->kernel and kernel->userspace work well
: in linux, but kernel->kernel interfaces seem to have  codepaths that
: aren't always tested that much.


According to the version numbers in the output of rpcinfo, I have nfs
v4 available on the server.  I have no idea if this makes a
difference, but serving a 700MB CD image via loopback has given me no
problems.

But for some reason I can't serve a DVD .iso image.  Of course your
solution of copying the loopback mounted directory into a real
directory is a workaround.  But what a waste of space!

It seems to me that serving a DVD .iso via NFS should be a fairly
commonly done thing.  Is anyone on this list successfully doing this?

Dean


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2005-06-05  6:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04  3:19 Help: nfs not able to mount large (loopback) directory Dean S. Messing
2005-06-04  4:26 ` Trond Myklebust
2005-06-05  6:00   ` Dean S. Messing
2005-06-04  5:28 ` Dan Stromberg
2005-06-05  6:07   ` Dean S. Messing [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=20050605060708.A7FF4112D0@pons \
    --to=deanm@sharplabs.com \
    --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 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.