Dashboard

Feb 03 19:20 | @jjmorganstern It's a slippery slope that vinyl. I should know; bought one record, house is now full of vinyl and 3 record players. ;-)
Feb 02 19:06 | Every time someone attempts to explain a joke to me for now on, I will throw water in your face. It'll be funnier than your explanation.
Feb 02 17:43 | Lot's of little interesting tests and tools coming out today. How much CSS3 does our browser support? http://t.co/Kq0mM9Hd

Reaching the limits

March 25th 2004

Ever wonder what the upper limits of the VX file system is (Sun Solaris 8 accessing in this case)? That is, how many links can you have in one directory (a link is roughly a file or folder)? Well, I found out yesturday in very hard fashion on a major work order system we built for a large wireless telecom.

The system has been in use for some three years, and has worked very well, providing much needed process improvements. For some time we’ve pushed for an archive feature that fell on deaf ears. Yesturday however, they hit the limit folder inode limit (32767) with a lovely error message that I couldn’t figure out (the web app only returned a CFdirectory error and doesn’t give you much to go on) which means the system could not create new work orders (I can’t explain how the system works, and why a folder is needed, but trust me, it is important and just can’t be turned off). I had never heard of this limit, and it took me some time to figure out that fixing the limit is not really not possible without risking file system corruption.

We did find a solution (requiring cleaver symlinking and clearing out empty folders). But if you ever see the error message “cannot create directory: too many links” you might find yourself in a bind.

Reader Responses

Skip to Response Form

Comment on this Entry

About This Entry

You are reading "Reaching the limits", and entry posted on 25 March, 2004 and filed under Uncategorized.

0 responses to this entry. 0 blog reactions. Add your response or trackback from your own site.