filesize limit "rolls over" to 0 kbytes at 4 GB

[Jonathan Dill <dill@xxxxxxxxxxxx>]

Todd Raeker wrote: 
>   Thanks for the info you provided.  I did as your suggest but then ran into
> a 4 GB limit.  Running limit under tcsh showed the 4 GB limit.  However, I
> should be able to unlimit the filesize but am ignored.  What do you get when
> you issue the limit command ?  Certainly 4 GB is better than 2 but I should
> not be limited as I think I am doing what I need.

(Just to refresh for the list, we recompiled tcsh with O_LARGEFILE to
get past the 2 GB filesize limit, but now "limit -h" shows a 4 GB
limit).

Hmm.  I see what you mean when I do "limit -h" it says the filesize
limit is 4194302 kbytes.  However, despite the advertised limit, I was
able to create a 4.7 GB file as root:

[root@localhost ~]# du -h /trans/mystery/20011025.home.0.gz
4.7G    /trans/mystery/20011025.home.0.gz

What's very odd is that the value seems to "roll over" to 0 kbytes at
precisely 4 GB:

[root@localhost ~]# limit -h
cputime         0:0-1
filesize        4194303 kbytes
datasize        4194303 kbytes
stacksize       4194303 kbytes
coredumpsize    4194303 kbytes
memoryuse       4194303 kbytes
descriptors     1024 
memorylocked    4194303 kbytes
maxproc         1535 
openfiles       1024 
[root@localhost ~]# limit -h filesize 4194304
[root@localhost ~]# limit -h
cputime         0:0-1
filesize        0 kbytes
datasize        4194303 kbytes
stacksize       4194303 kbytes
coredumpsize    4194303 kbytes
memoryuse       4194303 kbytes
descriptors     1024 
memorylocked    4194303 kbytes
maxproc         1535 
openfiles       1024 

If you keep increasing the limit, you get a modulus of 4 GB eg. 5 GB
gives you a limit of 1 GB, 37 GB gives you a limit of 1 GB etc.

Anybody have any ideas about this?

-- 
"Jonathan F. Dill" (dill@xxxxxxxxxxxx)