* Re: ftruncate64
[not found] ` <1vBDZ-48V-7@gated-at.bofh.it>
@ 2004-03-03 21:42 ` Bill Davidsen
0 siblings, 0 replies; 4+ messages in thread
From: Bill Davidsen @ 2004-03-03 21:42 UTC (permalink / raw)
To: Chris Wedgwood; +Cc: Linux Kernel Mailing List
Chris Wedgwood wrote:
> On Thu, Feb 26, 2004 at 05:23:10AM +0600, Anton Petrusevich wrote:
>
>
>>ftruncate64(1, 2199023255552) = -1 EFBIG (File too large)
>
>
> Depends on your fs, some fs's will allow you to create much larger
> files that others:
>
> cw@pain:~$ truncate -c -s100t big-file
> cw@pain:~$ ls -lh big-file
> -rw-r--r-- 1 cw cw 100T Mar 3 02:05 big-file
>
>
> Note, you might need a 64-bit system to be able to write to all of
> that because the index into the buffer-cache is an unsigned long. For
> me on my notebook I can't write past 8T.
If that's an issue I want a laptop like yours! Disk size aside, writing
8T would take longer than the MTBF of both the disk and the owner :-(
^ permalink raw reply [flat|nested] 4+ messages in thread
* ftruncate64
@ 2004-02-25 23:27 Anton Petrusevich
0 siblings, 0 replies; 4+ messages in thread
From: Anton Petrusevich @ 2004-02-25 23:27 UTC (permalink / raw)
To: linux-kernel
Hi guys,
Sorry guys, forgot about bs, 2Tb is large enough :)
--
Anton Petrusevich
^ permalink raw reply [flat|nested] 4+ messages in thread
* ftruncate64
@ 2004-02-25 23:23 Anton Petrusevich
2004-03-03 10:08 ` ftruncate64 Chris Wedgwood
0 siblings, 1 reply; 4+ messages in thread
From: Anton Petrusevich @ 2004-02-25 23:23 UTC (permalink / raw)
To: linux-kernel
Hi guys,
That looks funny:
casus@jabbervorx:~$ dd if=/dev/zero of=hole bs=1k count=1 seek=2047M
1+0 records in
1+0 records out
1024 bytes transferred in 0,000133 seconds (7696845 bytes/sec)
casus@jabbervorx:~$ dd if=/dev/zero of=hole bs=1k count=1 seek=2048M
dd: advancing past 2199023255552 bytes in output file `hole': File too large
strace shows the errorneous call:
ftruncate64(1, 2199023255552) = -1 EFBIG (File too large)
This behavour is observed with 2.4.23 and 2.6.3-rc1 kernels. And with
2.4.20-28.9smp redhat kernel too. But not with RHEL3 kernels. Looks like
RedHat silently fixed that bug.
--
Anton Petrusevich
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ftruncate64
2004-02-25 23:23 ftruncate64 Anton Petrusevich
@ 2004-03-03 10:08 ` Chris Wedgwood
0 siblings, 0 replies; 4+ messages in thread
From: Chris Wedgwood @ 2004-03-03 10:08 UTC (permalink / raw)
To: Anton Petrusevich; +Cc: linux-kernel
On Thu, Feb 26, 2004 at 05:23:10AM +0600, Anton Petrusevich wrote:
> ftruncate64(1, 2199023255552) = -1 EFBIG (File too large)
Depends on your fs, some fs's will allow you to create much larger
files that others:
cw@pain:~$ truncate -c -s100t big-file
cw@pain:~$ ls -lh big-file
-rw-r--r-- 1 cw cw 100T Mar 3 02:05 big-file
Note, you might need a 64-bit system to be able to write to all of
that because the index into the buffer-cache is an unsigned long. For
me on my notebook I can't write past 8T.
--cw
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-03-03 21:37 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1tgNg-8o9-5@gated-at.bofh.it>
[not found] ` <1vBDZ-48V-7@gated-at.bofh.it>
2004-03-03 21:42 ` ftruncate64 Bill Davidsen
2004-02-25 23:27 ftruncate64 Anton Petrusevich
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 23:23 ftruncate64 Anton Petrusevich
2004-03-03 10:08 ` ftruncate64 Chris Wedgwood
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox