From: Tim Tassonis <timtas@dplanet.ch>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fdisk: "File size limit exceeded on fdisk" 2.4.10 to 2.4.13-pre6
Date: Wed, 24 Oct 2001 18:00:39 +0200 [thread overview]
Message-ID: <E15wQSN-0000Hg-00@lttit> (raw)
In-Reply-To: <E15wQTJ-0001v1-00@the-village.bc.nu>
In-Reply-To: <E15wQDj-0000HT-00@lttit> <E15wQTJ-0001v1-00@the-village.bc.nu>
On Wed, 24 Oct 2001 17:01:37 +0100 (BST)
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> glibc 2.1.x has minimal support for 64bit file size handling. You
probably
> need to build 64bit aware tools. You might also be hitting a device bug
that
> seems to be in Linus kernel where devices are inheriting the file size
limit
> of the underlying fs the /dev node is on. However I thought that was
long
> fixed.
>
The latter seems to be the case because Vita Samel (hope I got this right)
just reported that "Booting into 2.4.10-ac10" fixed the problem. Perhaps
it once was fixed and later defixed?
Bye
Tim
next prev parent reply other threads:[~2001-10-24 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 15:09 fdisk: "File size limit exceeded on fdisk" 2.4.10 to 2.4.13-pre6 Tim Tassonis
2001-10-24 15:27 ` Alan Cox
2001-10-24 15:45 ` Tim Tassonis
2001-10-24 16:01 ` Alan Cox
2001-10-24 16:00 ` Tim Tassonis [this message]
2001-10-24 16:12 ` Alan Cox
2001-10-24 16:28 ` Mohammad A. Haque
2001-10-24 16:34 ` Tim Tassonis
2001-10-24 16:39 ` Mohammad A. Haque
2001-10-24 16:42 ` Mohammad A. Haque
2001-10-25 0:34 ` Tim Tassonis
2001-10-25 1:03 ` Mohammad A. Haque
2001-10-25 15:56 ` bill davidsen
2001-10-25 16:25 ` Mohammad A. Haque
2001-10-31 17:16 ` Bill Davidsen
2001-10-31 17:29 ` Mohammad A. Haque
2001-10-25 10:04 ` Vitezslav Samel
2001-10-24 15:40 ` Vitezslav Samel
2001-10-24 16:03 ` Gerhard Mack
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=E15wQSN-0000Hg-00@lttit \
--to=timtas@dplanet.ch \
--cc=alan@lxorguk.ukuu.org.uk \
--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