From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Zdenek Kabelac <kabi@fi.muni.cz>
Cc: linux-kernel@vger.kernel.org, bcollins@debian.org
Subject: Re: Bug in large files ext2 in 2.4.0-test11 ?
Date: Mon, 20 Nov 2000 19:06:07 MET-1 [thread overview]
Message-ID: <D697E1046DD@vcnet.vc.cvut.cz> (raw)
On 20 Nov 00 at 17:56, Zdenek Kabelac wrote:
> I just noticed this problem -
> I'm missing some large files created in the filesystem.
>
> This is 'ls' output from 2.4.0-test11/test10
> total 33
> drwxr-xr-x 6 root root 4096 Nov 20 18:06 .
> drwxr-xr-x 42 root root 1024 Nov 20 14:02 ..
> drwxr-xr-x 2 root root 4096 Nov 19 15:50 X
> drwxr-xr-x 2 root root 16384 Sep 30 18:45 lost+found
> ls: zero: Value too large for defined data type
>
> but maybe its incompatibility in libc - anyway I'm using
> uptodate Debian Woody if this helps.
It is problem with Debian's glibc, it is compiled with 2.2.x kernel
headers. I filled bugreport against this few weeks ago, but it was marked
as inappropriate because of Debian glibc is built against newest
kernel-headers package, and newest kernel-headers package is still 2.2.x.
Maybe someone (you) should fill bug against kernel-headers or kernel-source
to get 2.4.x into Debian. Then Ben Collins (Debian glibc maintainer) can
recompile and officially release glibc compiled against 2.4.x kernel.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
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 reply other threads:[~2000-11-20 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 19:06 Petr Vandrovec [this message]
2000-11-20 18:19 ` Bug in large files ext2 in 2.4.0-test11 ? Ben Collins
-- strict thread matches above, loose matches on Subject: below --
2000-11-20 19:32 Petr Vandrovec
2000-11-20 19:16 ` Ben Collins
2000-11-20 19:42 ` Matti Aarnio
2000-11-20 19:44 ` Ben Collins
2000-11-20 22:59 ` Wichert Akkerman
2000-11-21 11:24 ` Meelis Roos
2000-11-20 17:56 Zdenek Kabelac
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=D697E1046DD@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=bcollins@debian.org \
--cc=kabi@fi.muni.cz \
--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