From: "Dean S. Messing" <deanm@sharplabs.com>
To: trond.myklebust@fys.uio.no
Cc: nfs@lists.sourceforge.net
Subject: Re: Help: nfs not able to mount large (loopback) directory
Date: Sat, 4 Jun 2005 23:00:00 -0700 (PDT) [thread overview]
Message-ID: <20050605060000.61C2C112D0@pons> (raw)
In-Reply-To: <1117859180.11099.12.camel@lade.trondhjem.org> (message from Trond Myklebust on Sat, 04 Jun 2005 00:26:20 -0400)
Trond Myklebust wrote:
: fr den 03.06.2005 Klokka 20:19 (-0700) skreiv Dean S. Messing:
: >
: > 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?
:
: It is true that NFS version 2 cannot handle files > 2GB, but as far as I
: gathered you are not exporting the ISO as a single file. Besides, NFSv3
: and NFSv4 should be quite capable of dealing with a 4GB file.
:
: This therefore sounds more like it might be some strange interaction
: between the loopback driver and nfsd or mountd.
>From my reading your remarks sound correct. I wonder how I can
fix this problem. Loopback mounting a DVD .iso image and making
it available via NFS has got to be something that is fairly commonly
done.
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
next prev parent reply other threads:[~2005-06-05 6:00 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 [this message]
2005-06-04 5:28 ` Dan Stromberg
2005-06-05 6:07 ` Dean S. Messing
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=20050605060000.61C2C112D0@pons \
--to=deanm@sharplabs.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.