User unable to create a file over 2 GB's in size

UNIX AIX
1

Hello, this is my first post.

I have a user who cannot create a file over 2 GB's in size eventhough the FS is large file enabled and I added a special stanza in /etc/security/limits to allow an unlimited file size for this particular user (user1 - see below).

ibm:/home/root (4062)#cat /etc/security/limits

*

  • Sizes are in multiples of 512 byte blocks, CPU time is in seconds
    *
  • fsize - soft file size in blocks
  • core - soft core file size in blocks
  • cpu - soft per process CPU time limit in seconds
  • data - soft data segment size in blocks
  • stack - soft stack segment size in blocks
  • rss - soft real memory usage in blocks
  • nofiles - soft file descriptor limit
  • fsize_hard - hard file size in blocks
  • core_hard - hard core file size in blocks
  • cpu_hard - hard per process CPU time limit in seconds
  • data_hard - hard data segment size in blocks
  • stack_hard - hard stack segment size in blocks
  • rss_hard - hard real memory usage in blocks
  • nofiles_hard - hard file descriptor limit
    *
  • The following table contains the default hard values if the
  • hard values are not explicitly defined:
    *
  • Attribute Value
  • ========== ============
  • fsize_hard set to fsize
  • cpu_hard set to cpu
  • core_hard -1
  • data_hard -1
  • stack_hard -1
  • rss_hard -1
  • nofiles_hard -1
    *
  • NOTE: A value of -1 implies "unlimited"
    *

default:
fsize = 4194300
core = 4096
cpu = -1
data = 524288
rss = 131072
nofiles = 2000

root:

daemon:

bin:

sys:

adm:

uucp:

guest:

nobody:

lpd:

user1:
fsize = -1

I'm not sure where else to look to resolve this issue.

Thanks,
Shane

2

I do not use AIX so I won't be much help. But here are a few thoughts anyways... Can root create a big file in that filesystem? You might have a program /usr/bin/ulimit. If so have the user run /usr/bin/ulimit -a and post the results. Some shell also have a built-in ulimit with no -a, so you really may need a path to the program. On most OS'es, I would expect the user to need to log off and back on to get the values..was that done?

The answers to this stuff may help when a AIX expert comes along.

3

After I made the changes in the limits file I had the user log off and back in, but got the same results. I'll have to test to see if root can create a file over 2 GB's.

Below is the ulimit -a command as ran by the user.

$ ulimit -a
time(seconds) unlimited
file(blocks) 4194272
data(kbytes) 262144
stack(kbytes) 16384
memory(kbytes) unlimited
coredump(blocks) 4096
nofiles(descriptors) 2000

Thanks,
Shane

4

The "file(blocks) 4194272" is the problem. Somehow that change you made did not take. There is a lsuser command, you might try that to see what fsize and fsize_hard are at. You may need to set fsize_hard to -1 as well.

5

What is weird is when I issue the lsuser command on the user, it shows the fsize is set to -1. But when I issue the ulimit -a command as the user, the fsize is 4194272???

Thanks,
Shane

6

What does lsuser say about fsize_hard?

7

vi /etc/security/limits
this will change on reboot and become prmanent but to change it on the fly
with out rebooting use the following

chuser rss=<value> <username>
chuser fsize=<value> <username>
chuser data=<value> <username>

After reboot this will revert back to what is in /etc/security/limits

+===========================================
Other problems with file system and sizes may be that you have to create an enhanced o ( or big file enabled filesystem ) but you will have to look at what you have set in fs

http://publibn.boulder.ibm.com/doc\_link/en\_US/a\_doc\_lib/aixbman/admnconc/jfs\_size_under.htm\#HDRD6CE066274MEKI

8

Thanks everyone for the help. It turns out the job was a batch job that was actually running under root. So, I modified root's fsize to -1 and all is well. Also, after I changed /etc/security/limits, all I had to do was log out and back in for the changes to take effect.

Thanks,
Shane