Hello,
I believe the following is true, correct me if it is not:
If more than one objects reference a block (e.g. 2 files have the same block
open)
there must be multiple clones of the arc_buf_t ( and associated dmu_impl_t )
records
present, one for each of the objects. This is always so, eve
Hi Jeremy,
Jeremy Archer wrote:
> Hello,
>
> I believe the following is true, correct me if it is not:
>
> If more than one objects reference a block (e.g. 2 files have the same block
> open)
> there must be multiple clones of the arc_buf_t ( and associated dmu_impl_t )
> records
> present, o
Thanks for the explanation.
> a dirty
> buffer goes onto the
> list corresponding to the txg it belongs to.
Ok. I see that all dirty buffers are put on a per txg list.
This is for easy synchronization, makes sense.
The per dmu_buf_impl_t details are a bit fuzzy.
I see there can be m
On Mon, Jun 22, 2009 at 02:28:25PM -0700, Jeremy Archer wrote:
>
> Also: what is BP_IS_HOLE? I see it has no birth_txg.
A "HOLE" BP is similar to a NULL pointer; it doesn't point to anything, and
is used to indicate there is no data underneath that block pointer. The
representation is all-zeros
gary mazz wrote:
> Hi,
>
> I'd like to use ZFS in a highly scalable data application.
>
> My requirements are very loose at this point. but I know I need object
> locking and I'd like to use the DMU interface. I would like the DMU
> transactions to be distributed across machines ? The preferr
