I'm really curious what specific situations cause this, as I've had filers
run out of space on vol0 lots of times and have never had a panic from it.
The problem we have is that we just can't justify giving up three disks
worth of data to hold the very tiny amount of data needed for booting. Our
engineers are data hungry monsters, gobbling up as much space as they can,
no matter how much space we provide.
If it wasn't for occasionally running out of space, I'm not sure we'd ever
be able to force them to delete stuff.
--
Mike Sphar - Sr Systems Administrator - Remedy, a BMC Software Company
-----Original Message-----
From: Rune Bakken [mailto:rb@telenor.net]
Sent: Tuesday, February 11, 2003 3:25 PM
To: Charles Bartels
Cc: toasters@mathworks.com
Subject: Re: using vol0
Charles Bartels
cbartels@openharbor.com writes:
> Hi,
>
> I'm configuring an F810 and space is going to be a little tight. How do
> people feel about adding disks to vol0 and using that instead of creating
a
> whole separate volume (and burning a another parity disk) ?
Not sure if it is an issue, but I will never have any production data
that keeps growing on vol0 again. I had a Filer panic once or twice
because vol0 got filled up.
I know some admins on this lists put static data that they control on
with a qtree with fixed size (tree quota) on vol0.
>>>>>>>>>>.rune
--
Rune Bakken
Senior System Administrator
Telenor Business Solutions (Nextra), ManagedServices/*/IP-Services
http://ips.telenor.net/