2.4.0-test9 + LFS
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.
Signature · 5 lines
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 [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 9 lines · Wakko Warner
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 typeNOTE: 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.
-ben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 9 lines · Wakko Warner
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 typeNOTE: 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.
Your userspace tools are not using LFS compliant open(O_LARGEFILE), and stat64() methods.
EXT2 got corrected to do LFS limited open() handling at correct limit (2G-1) at around that time.
There still lurks some mis-compliance issues at read() and write() which are still allowed to go over 2G-1 marker without the fd having O_LARGEFILE flag.
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 7 lines
Quoted 7 lines
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
Quoted 7 lines
Quoted 2 lines
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.
Signature · 5 lines
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 [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 1 line · Wakko Warner
I did upgrade that and it didn't help anything.
Was your glibc compiled against 2.4 kernel headers?
-ben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 3 lines
Quoted 1 line
I did upgrade that and it didn't help anything.
Was your glibc compiled against 2.4 kernel headers?
That I do not know. it's v 2.1.99 that came with debian in the past week or so
Signature · 5 lines
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 [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 6 lines · Wakko Warner
Quoted 3 lines
Quoted 1 line
I did upgrade that and it didn't help anything.
Was your glibc compiled against 2.4 kernel headers?
That I do not know. it's v 2.1.99 that came with debian in the past week or so
Then it's compiled against the v2.2 kernel headers.
/David
_ _
// David Weinehall <[email protected]> /> Northern lights wander \\
// Project MCA Linux hacker // Dance across the winter sky // \> http://www.acc.umu.se/~tao/ </ Full colour fire </
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 6 lines · David Weinehall
Quoted 2 lines · Wakko Warner
That I do not know. it's v 2.1.99 that came with debian in the past week or so
Then it's compiled against the v2.2 kernel headers.
That explains why LFS isn't working then. I strongly suggest that the Debian glibc maintainers compile against 2.4 kernel headers or patch their 2.2 kernel headers to include the LFS stubs.
-ben
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/