On Tue, Jul 04, 2006 at 09:10:11AM +0200, Constantin Gonzalez wrote: > Hi Eric, > > Eric Schrock wrote: > > You don't need to grow the pool. You should always be able truncate the > > file without consuming more space, provided you don't have snapshots. > > Mark has a set of fixes in testing which do a much better job of > > estimating space, allowing us to always unlink files in full pools > > (provided there are no snapshots, of course). This provides much more > > logical behavior by reserving some extra slop. > > is this a planned and not yet implemented functionality or why did Tatjana > see the "not able to rm" behaviour?
As I mentioned, Mark has a set of fixes in testing. They should be available sometime in the near future. In the meantime, you can truncate large files to free up space instead - because these don't involve rewriting the parent directory pointers, this should always work. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
