From: Wakko Warner <wakko@animx.eu.org>
To: kernel@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test9 + LFS
Date: Fri, 27 Oct 2000 06:48:31 -0400 [thread overview]
Message-ID: <20001027064831.A20958@animx.eu.org> (raw)
In-Reply-To: <20001026215606.A19958@animx.eu.org> <Pine.LNX.3.96.1001026231315.22907A-100000@kanga.kvack.org>
In-Reply-To: <Pine.LNX.3.96.1001026231315.22907A-100000@kanga.kvack.org>; from kernel@kvack.org on Thu, Oct 26, 2000 at 11:15:13PM -0400
> > I attempted to create a 4gb sparce file with dd. It failed.
> > I created one that was 2.1gb in size which worked. Then I appeneded more
> > junk to the end of the file making it over 2.2gb.
> >
> > doing an ls -l shows:
> > ls: x: Value too large for defined data type
> >
> > NOTE: this worked in 2.4.0-test6 and I believe it stopped working around
> > test8, but I'm not sure. May have been around test7.
>
> Previous kernels allowed up to 4gb to be returned by the old stat.
> Upgrade your glibc and fileutils -- most recent distributions (Red Hat,
> SuSE, ...) are LFS ready, and the only reports I've seen about this
> concerned Slackware.
I did upgrade that and it didn't help anything.
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-10-27 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 1:56 2.4.0-test9 + LFS Wakko Warner
2000-10-27 3:15 ` kernel
2000-10-27 10:48 ` Wakko Warner [this message]
2000-10-27 14:42 ` kernel
2000-10-27 16:19 ` Wakko Warner
2000-10-27 16:15 ` David Weinehall
2000-10-27 16:24 ` kernel
2000-10-27 8:14 ` Matti Aarnio
-- strict thread matches above, loose matches on Subject: below --
2000-10-27 15:05 Petr Vandrovec
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=20001027064831.A20958@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=kernel@kvack.org \
--cc=linux-kernel@vger.kernel.org \
/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