From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: Takashi Sato <sho@tnes.nec.co.jp>,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/3] Fix problems on multi-TB filesystem and file
Date: Fri, 16 Dec 2005 15:37:11 -0500 [thread overview]
Message-ID: <1134765431.7941.3.camel@lade.trondhjem.org> (raw)
In-Reply-To: <2cd57c900512161224i1079572ao@mail.gmail.com>
On Sat, 2005-12-17 at 04:24 +0800, Coywolf Qi Hunt wrote:
> >
> > It may surprise you to learn that not all network filesystems are block
> > based.
> >
> > NFS has no truck with CONFIG_LBD at all.
>
> I thought no network filesystems are block based from a client
> viewpoint. (There's a network block driver though.) Client kernel
> needn't enable LBD.
Without this patch, the client _would_ have to enable LBD if it wanted
to correctly report the size of a large disk on the remote server.
The main point, though is that sector_t is a handle to a block. It is
_NOT_ the right type to use for reporting a disk size.
Cheers,
Trond
next prev parent reply other threads:[~2005-12-16 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 13:11 [PATCH 3/3] Fix problems on multi-TB filesystem and file Takashi Sato
[not found] ` <2cd57c900512161139n7d738415q@mail.gmail.com>
2005-12-16 19:57 ` Trond Myklebust
[not found] ` <2cd57c900512161224i1079572ao@mail.gmail.com>
2005-12-16 20:37 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 10:05 Takashi Sato
2006-01-13 2:33 ` Andrew Morton
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=1134765431.7941.3.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=coywolf@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sho@tnes.nec.co.jp \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).