If you are referring to shrinking a pool/file system, where I work this is 
considered very high on the list. It isn't a truly dynamic file system if we 
can't shrink it.

As a practical example, you have a test server with several projects being 
worked on. When a project finishes 9for whatever reason), you delete the files, 
shrink the pool, and give the LUN back to the storage folks to assign to 
another server that may be running out of space.

Having a SAN, we see it as more important than, say, the RAIDZ work. But, I can 
see why other people with different needs will argue otherwise. There are other 
things I would like to see as well (ability to find what files got corrupted 
due to a HW failure, and so on--see my other threads in this forum), but from 
the enterprise perspective of the company I work for, this is right up there. 
Just throwing our $.02 in. :-)

Rainer
 
 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to