volume management

[Pawel Jakub Dawidek]

On Tue, Apr 10, 2007 at 01:32:02PM +0200, Ivan Voras wrote:
> Pawel Jakub Dawidek wrote:
> 
> >Ivan, as you probably already find out this is not an easy task and it
> >gets more complex when SU comes into play or any async operations,
> >because there is noone waiting for the error to return.
> >Maybe you for now allow to set two modes of handling ENOSPC
> >(configurable by the user):
> >1. Panic if there is no physical storage. This way you protect
> >   consistency. You already printed a warning that gvirstor is running
> >   out of physical storage, so administrator has a chance to do the job.
> 
> I really don't want to do that :(

If you have important data, this is really not bad idea. I, for one,
prefer my kernel to panic, so I can see what exactly went wrong, add
another disk and reboot instead of allowing kernel goes into wild by
returning an error which won't be handled properly.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20070410/919b5150/attachment.pgp