From: Zdenek Kabelac <kabi@fi.muni.cz>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Subject: Bug in large files ext2 in 2.4.0-test11 ?
Date: Mon, 20 Nov 2000 17:56:50 GMT [thread overview]
Message-ID: <3A1965E2.6BE6AF2@fi.muni.cz> (raw)
Hi
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
And this is same directory with 2.2.17pre9
total 4561569
drwxr-xr-x 6 root root 4096 lis 20 18:06 .
drwxr-xr-x 42 root root 1024 lis 20 14:02 ..
drwxr-xr-x 2 root root 16384 zář 30 18:45 lost+found
drwxr-xr-x 2 root root 4096 lis 19 15:50 X
-rw-r--r-- 1 root root 4294967295 lis 20 18:08 zero
Thought the 'zero' file has been created in 2.4.0-test11
I can't see it again with this kernel.
I would assume this is some problem of the kernel,
but maybe its incompatibility in libc - anyway I'm using
uptodate Debian Woody if this helps.
bye
--
There are three types of people in the world:
those who can count, and those who can't.
Zdenek Kabelac http://i.am/kabi/ kabi@i.am {debian.org; fi.muni.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:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-20 17:56 Zdenek Kabelac [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-20 19:06 Bug in large files ext2 in 2.4.0-test11 ? Petr Vandrovec
2000-11-20 18:19 ` Ben Collins
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
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=3A1965E2.6BE6AF2@fi.muni.cz \
--to=kabi@fi.muni.cz \
/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