Agreed. You can't want more than 1 inode per 4K WAFL block, right?
This application generates reports by generating directories. Each report
can generate hundreds of directories on the filer. I don't know why it
works this way but I'm told changing it will be quite a headache.
So, all these directories take up lots and lots of inodes, but no real space
on the filer.
Tom
-----Original Message-----
From: Chris Thompson [mailto:cet1@cus.cam.ac.uk]
Sent: Tuesday, April 03, 2001 4:25 PM
To: MadDog(a)fool.com
Cc: toasters(a)mathworks.com
Subject: Re: Inodes a go go
MadDog(a)fool.com (Tom \"Mad Dog\" Yergeau) writes:
>
> Okay, so the maximum number of inodes is 95% of the true (not usable) size
> of a volume divided by four.
>
> And if you're daring enough to type this into your filer, it will tell you
> that anyway:
>
> usvasvfile-001> maxfiles inquisition 50000000000000000
> Max inode count cannot exceed 201249946
>
>
> Now here's the problem. I just passed this information on to the
developers
> who wrote the program that uses up this exceedingly ridiculous number of
> inodes, and they tell me that they are going to start using them up even
> faster than in the past, and we may run out within six months, and is
there
> anything we can do to get more inodes?
>
> I suggested they re-write their program to not generate tens of thousands
of
> directories every day, but I don't know how well that will fly.
>
> Can anyone think of a way to get more inodes? NetApp folks, any hope a
RFE
> for a higher inode limit would go through?
Ummm... can you tell us more about this application that eats thousands
of inodes for breakfast every day? What are the contents of these inodes?
One would normally expect every inode to have at least one 4K block of
data associated with it unless
1. It is a regular file with length <= 64 bytes (fits in the inode).
2. It is a symbolic link with length <= 64 bytes (ditto).
3. It is a device, or socket, or named pipe, or some other implictly
zero-length object.
That is presumably the rationale behind NetApp's "you can't possibly
want more than 1 inode per 4 KB of data, can you?" upper limit.
Chris Thompson University of Cambridge Computing Service,
Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG,
Phone: +44 1223 334715 United Kingdom.