From: volodya@mindspring.com
To: Alexander Viro <viro@math.psu.edu>
Cc: Adam Schrotenboer <ajschrotenboer@lycosmail.com>,
lkml <linux-kernel@vger.kernel.org>,
reiser@namesys.com
Subject: Re: Stability of ReiserFS onj Kernel 2.4.x (sp. 2.4.[56]{-ac*}
Date: Sun, 15 Jul 2001 21:22:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.20.0107152104290.1295-100000@node2.localnet.net> (raw)
In-Reply-To: <Pine.GSO.4.21.0107152051340.24930-100000@weyl.math.psu.edu>
On Sun, 15 Jul 2001, Alexander Viro wrote:
>
>
> On Sun, 15 Jul 2001 volodya@mindspring.com wrote:
>
> > Umm that is very interesting - I was rather sure there were some problems
> > a while ago (2.2.x ?). Is there anything special necessary to use large
> > files ? Because I tried to create a 3+gig file and now I cannot ls or rm
> > it. (More details: the file was created using dd from block device (tried
> > to backup a smaller ext2 partition), ls and rm say "Value too large for
> > defined data type" and I upgraded everything mentioned in Documentation/Changes).
>
> <shrug> you need fileutils built with large file support enabled (basically,
> it should use stat64(), etc. and pass O_LARGEFILE to open()) and you need
> sufficiently recent libc. But that's the same regardless of fs type.
>
May I ask where does one get a patched fileutils package ? I have just
downloaded fileutils-4.1 from prep.ai.mit.edu and it has 0 information in
README, configure --help, etc on how to enable this and when compiled ls
still complains.
thanks !
Vladimir Dergachev
next prev parent reply other threads:[~2001-07-16 1:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 23:54 Adam Schrotenboer
2001-07-15 0:01 ` Thomas Zimmerman
2001-07-15 16:00 ` volodya
2001-07-15 16:08 ` Alexander Viro
2001-07-16 0:50 ` volodya
2001-07-16 0:54 ` Ragnar Kjørstad
2001-07-16 0:57 ` Alexander Viro
2001-07-16 1:22 ` volodya [this message]
2001-07-16 1:48 ` Ignacio Vazquez-Abrams
2001-07-15 16:33 ` Alan Cox
2001-07-15 16:44 ` Hans Reiser
2001-07-15 16:46 ` Alan Cox
2001-07-15 17:54 ` Hans Reiser
2001-07-15 18:17 ` Alan Cox
2001-07-16 13:27 ` Marco Colombo
2001-07-15 17:58 ` Rob Turk
2001-07-15 21:30 ` Daniel Phillips
2001-07-15 22:05 ` Hans Reiser
2001-07-15 22:18 ` Daniel Phillips
2001-07-16 0:22 ` Albert D. Cahalan
2001-07-16 12:49 ` Daniel Phillips
2001-07-17 19:40 ` Rob Landley
2001-07-16 17:19 ` Jussi Laako
2001-07-16 17:53 ` Daniel Phillips
2001-07-16 19:16 ` Hans Reiser
2001-07-16 21:00 ` Jussi Laako
2001-07-16 22:28 ` Daniel Phillips
2001-07-18 0:58 ` Dan Hollis
2001-07-16 4:39 ` Mike A. Harris
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=Pine.LNX.4.20.0107152104290.1295-100000@node2.localnet.net \
--to=volodya@mindspring.com \
--cc=ajschrotenboer@lycosmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®