Re: [zfs-discuss] Question about (delayed) block freeing

2010-10-29 Thread George Wilson
This value is hard-coded in. - George On Fri, Oct 29, 2010 at 9:58 AM, David Magda wrote: > On Fri, October 29, 2010 10:00, Eric Schrock wrote: > > > > On Oct 29, 2010, at 9:21 AM, Jesus Cea wrote: > > > >> When a file is deleted, its block are freed, and that situation is > >> committed in the

Re: [zfs-discuss] Question about (delayed) block freeing

2010-10-29 Thread David Magda
On Fri, October 29, 2010 10:00, Eric Schrock wrote: > > On Oct 29, 2010, at 9:21 AM, Jesus Cea wrote: > >> When a file is deleted, its block are freed, and that situation is >> committed in the next txg. Fine. Now those blocks are free, and can be >> used in new block requests. Now new requests com

Re: [zfs-discuss] Question about (delayed) block freeing

2010-10-29 Thread Eric Schrock
On Oct 29, 2010, at 9:21 AM, Jesus Cea wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, everybody. > > I have a question about the inner working of ZFS. Hope somebody can > provide some light. > > ZFS keeps 128 uberblocks around, just in case the last transactions are > corrupt

[zfs-discuss] Question about (delayed) block freeing

2010-10-29 Thread Jesus Cea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, everybody. I have a question about the inner working of ZFS. Hope somebody can provide some light. ZFS keeps 128 uberblocks around, just in case the last transactions are corrupted for any reason. My question is about block freeing. When a file