Hello Managers:
I'd like to thank the following people for their suggestions and helpful
information:
Tom Korenek
J. Dean Brock
Steven Hancock
Nickola Milutinovic
Dr Tom Blinn
Rasal Kumarage
Bryan Lavelle
Bob Vickers
Jonathan Nicholson
alan_at_nabeth.cxo.dec.com
Basically, everyone told me that I was correct in that I ran into a "BMT
exhaustion" which is similar to running out of inodes. It is a common
problem on systems that regularly create and delete very large numbers
of small files, which is exactly what we are doing. You can check how
many extents with the command
# showfile -x /[filesystem]/.tags/M-6
Some people did agree to use mkfdmn and addvol with the -x and -p
switches to increase the number of file system blocks. This would have
required the ADVFS-UTILITIES license. They suggested backing up the
entire domain and recreating the domain and filesets with the
appropriate parameters then restoring the data.
A less "intrusive" suggestion that may or may not work (depending on who
you ask) was to defragment the filesystem. Which would be a good idea
anyway, because our machine seems
highly fragmented right now.
Mr. Steven Hancock provided me with a very excellent paper describing
the problem and several solutions to the problem. With Mr. Hancock's
permission, I'll send anyone a copy if they ask me for it.
Unfortunately at the moment, we are in peak demand season, and unable to
down the machine. We have a temporary workaround through the use of an
available filesystem and symbolic links.
I'd like to thank everyone for their responses and offers for more
assistance. This is an extremely helpful group.
Kevin
[Original Query]
> We have an ES40 running Tru64 4.0f with a RAID unit attached to it. We
> have about 175 Gigs of space on the offending file domain. Even though
> it is up to 61% capacity, I am getting the error message
>
> :no space left on device
>
> I suspect that there are too many metadata extents (like inodes),
> because our data is an ENORMOUS amount of small files (possibly in the
> millions). From the man, I can increase the number of metadata table
> extent page with 'addvol -x' but I'm getting the following error:
>
> ERROR: This application will not run successfully unless it is used
> on the processor(s) on which it is licensed. The licensed processor(s)
> is the one on which the product requiring the PROD_ADV PAK
> will execute. An ADVFS-UTILITIES PAK must be registered in the License
> Database and activated in the kernel cache before this application
> will run. Refer to the installation guide for the product requiring
> the ADVFS-UTILITIES PAK for license database PAK registration
> instructions.
>
> So my question is, am I right as to why I'm getting the "no space left
> on device" error? Am I correct about the way to fix it is by using
> 'addvol -x'? And if it is, I guess I need a ADVFS-UTILITIES PAK
> registered, right? Finally, is there any other way around this problem,
> if I can't get a license right away?
--
Kevin Dea
System Administrator
Alpine Electronics Research of America
Received on Tue Jan 09 2001 - 18:06:26 NZDT