Hi,
I always thought the max. filesize limit for ReiserFS (v3.6) was 8 TiB
on x86_32 (and 4 GB for v3.5). Now I wanted to create a file bigger than
4GB and got:
# dd if=/dev/zero of=file.img bs=1M count=6144
File size limit exceeded (core dumped)
Attaching gdb(1) to the coredump:
[...]
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
Core was generated by `dd if /dev/zero of file.img bs 1M count 6144'.
Program terminated with signal 25, File size limit exceeded.
#0 0xb7f50410 in __kernel_vsyscall ()
(gdb) bt full
#0 0xb7f50410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7eb8d23 in ?? ()
No symbol table info available.
# ls -l file.img
-rw------- 1 root root 4294966272 2007-11-07 21:16 file.img
(that's 4*1024^3 - 1024)
When strace(1)'ing dd(1), I can see:
mmap2(NULL, 1539648, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7c26000
close(3) = 0
close(0) = 0
open("/dev/zero", O_RDONLY|O_LARGEFILE) = 0
_llseek(0, 0, [0], SEEK_CUR) = 0
close(1) = 0
open("file.img", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 1
So, O_LARGEFILE is set - why wouldn't it work? I'm using 2.6.23.1, I've
reiserfsck'ed the device, but no errors were shown. I *think* I've created
files > 4 GB in the past, but I cannot remember if I did this on x86 and
on reiserfs.
Any ideas what's going on?
Thanks
Christian.
--
BOFH excuse #274:
It was OK before you touched it.
-
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
