From: Benjamin LaHaise <bcrl@redhat.com>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Barubary <barubary@cox.net>,
linux-kernel@vger.kernel.org,
Rick Stevens <rstevens@vitalstream.com>
Subject: Re: Big file support
Date: Thu, 28 Feb 2002 10:22:24 -0500 [thread overview]
Message-ID: <20020228102224.G8011@redhat.com> (raw)
In-Reply-To: <3C7D3587.8080609@vitalstream.com> <006301c1bfc9$a5c6de90$a7eb0544@CX535256D> <20020227223426.N23151@mea-ext.zmailer.org>
In-Reply-To: <20020227223426.N23151@mea-ext.zmailer.org>; from matti.aarnio@zmailer.org on Wed, Feb 27, 2002 at 10:34:26PM +0200
On Wed, Feb 27, 2002 at 10:34:26PM +0200, Matti Aarnio wrote:
> There are several filesystems which are 64-bit/large-file supporting,
> but also some which are inherently incapable to exceed 2G or 4G.
>
> It looks like the LOOP driver lands in between -- it should be LFS
> capable, but it isn't.
Loop is LFS capable. I know that we shipped LFS enabled loop utilities
for 7.2, probably 7.1 as well. They were missed in the first batch of
LFS conversions, and several distributions are lagging behind in this
area.
-ben
next prev parent reply other threads:[~2002-02-28 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 19:37 Big file support Rick Stevens
2002-02-27 20:00 ` Jon
2002-02-27 20:02 ` Barubary
2002-02-27 20:31 ` Alan Cox
2002-02-28 12:47 ` Big file support (emperical evidence) Stephen Samuel
2002-02-27 20:34 ` Big file support Matti Aarnio
2002-02-27 21:33 ` Big file support\ Chris Wedgwood
2002-02-28 15:22 ` Benjamin LaHaise [this message]
2002-02-27 21:44 ` Big file support Rik van Riel
2002-02-28 5:47 ` Andreas Jaeger
2002-02-28 21:58 ` Bill Davidsen
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=20020228102224.G8011@redhat.com \
--to=bcrl@redhat.com \
--cc=barubary@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=rstevens@vitalstream.com \
/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