We have run into a problem this morning with an advfs configuration.
We have a raid array 8000 with a 72Gb partiton. We have several advfs filesets mounted onto these, with 100 directories in each and then lots of small binary files in each. This morning for no reason the fileset has stopped allowing any new data being written into it, but a df -k shows that there should be 32Gb still available. We have an identical 72 gb partion on the same raid array, and have filled this to 100% , but not with so many individual small files, without problems which leads me to suspect that we have blown a file count limit somewhere.
df -k looks like this,
raidr1#2001-04 71095408 932 36221288 1% /images/2001/04
raidr1#2001-05 71095408 2856 36221288 1% /images/2001/05
raidr1#2001-06 71095408 7354003 36221288 17% /images/2001/06
raidr1#2001-07 71095408 13238815 36221288 27% /images/2001/07
raidr1#2001-08 71095408 8292806 36221288 19% /images/2001/08
raidr1#2001-09 71095408 25 36221288 1% /images/2001/09
raidr1#2001-10 71095408 17 36221288 1% /images/2001/10
Does anyone know what if any other limits we may have hit? I don't think advfs has inodes? Any sugesstions greatly received.
Bryan Mills.
This message is intended only for the use of the person(s) ("The intended
Recipient(s)") to whom it is addressed. It may contain information which
is privileged and confidential within the meaning of applicable law. If
you are not the intended recipient, please contact the sender as soon as
possible. The views expressed in this communication are not necessarily
those held by LYNX Express Limited.
Received on Tue Aug 21 2001 - 08:24:36 NZST