When I've needed more space for the client indexes I have just moved some 
of them to a new partition and then put a symbolic link in. Our indexes 
don't get to the size of yours but I think I would do the same thing.

On Thu, 28 Sep 2006 08:57:47 -0400, Teresa Biehler <tpbsys AT RIT DOT EDU> 
wrote:

>As we've added more and more clients, our /nsr/index directory has
>gotten large (200 GB).  We need to create more space for the client
>index directories and are weighing the pros and cons of expanding
>/nsr/index vs creating a new file system and moving some of our clients
>to that alternate location.
>
> 
>
>For those of you with large environments, how do you manage space for
>/nsr/index?  Do you use a single file system (i.e. all the client index
>files into /nsr/index)?  If so, have you had problems with reboots
>causing long outages while that file system is checked (assuming you are
>using ufs)?  Do you move some client index directories to alternate
>locations and use the "client index path" field in the client
>definition?  If so, do you find this difficult to manage?  Have you
>needed to create any special processes to handle this?
>
> 
>
>Thanks.
>
>Teresa
>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER