If you have shell access, check out man quota.

Update: In a past life, fraught with student users who thought Unix was spelled with an 'E', I enforced some pretty harsh quotas for new accounts. These were, however, relaxed into a larger pool for the asking, and could even be expanded to some pretty extreme values with a faculty sponsor (for research or the like). I would typically not refuse requests into the larger pools (my job was to support the education), and automation (quite a bit with Perl, IIRC) made applying these quota pools very easy and flexible. They were set up to avoid non-terminating loops from filling the user file systems, and keep the student Unix network more reliable.

Assuming that quotas are in place, talk to your vendor. They may have a quota in place to help keep one customer from impacting another (at least without giving the admins time to respond). If this is the case, they may not have a problem with either (1) raising your quota (perhaps for a price), or (2) you storing some select files in a filestore of some sort, for example, a ZIP, YAML, DBM::Deep, or some other type of file.

It may also be time to re-architect how you are storing your data files.

--MidLifeXis

In reply to Re: Inode 8000 limitation by MidLifeXis
in thread Inode 8000 limitation by vit

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.