From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Martin Siegert <siegert@sfu.ca>
Cc: nfs@lists.sourceforge.net
Subject: Re: limit on filesystem size?
Date: Sat, 3 Aug 2002 00:35:55 +0200 [thread overview]
Message-ID: <15691.2379.954309.55464@charged.uio.no> (raw)
In-Reply-To: <20020802202210.GA28263@stikine.ucs.sfu.ca>
>>>>> " " == Martin Siegert <siegert@sfu.ca> writes:
> Please, bear with me - I am by no means an expert on these
> issues. But my impression was that the problem is in
> include/linux/blkdev.h
> struct request { ...
> unsigned long sector;
> with results in a (local) filesystem size limit of 2TB (unless
> sectors larger than 512 bytes are used).
> Am I understanding correctly that you are telling me that this
> does not apply to NFS and that despite this definition I could
> even reexport (user space NFS?) such a filesystem?
I repeat: yes!
NFS does not know anything about sectors. It indexes *files* by means
of an opaque 32-byte (NFSv2) or 64-byte (v3) filehandle. The latter
can be considered to be the equivalent of 'file descriptors' as used
by libc does in open()/read()/write().
Rexporting filesystems is never a good idea though. Better to allow
all NFS clients direct access to the server...
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-08-02 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 19:53 limit on filesystem size? Martin Siegert
[not found] ` <shs7kja48km.fsf@charged.uio.no>
2002-08-02 20:22 ` Martin Siegert
2002-08-02 22:35 ` Trond Myklebust [this message]
2002-08-02 21:26 ` Steve Costaras
2002-08-02 21:43 ` Ragnar Kjørstad
2002-08-02 21:52 ` Martin Siegert
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=15691.2379.954309.55464@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=siegert@sfu.ca \
/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.