Bill Moloney wrote:
Thanks for the input Darren, but I'm still confused about DNODE
atomicity ... it's difficult to imagine that a change that is made
anyplace in the zpool would require copy operations all the way back
up to the uberblock
This is in fact what happens. However, these changes
> Thanks for the input Darren, but I'm still confused about DNODE
> atomicity ... it's difficult to imagine that a change that is made
> anyplace in the zpool would require copy operations all the way back
> up to the uberblock (e.g. if some single file in one of many file
> systems in a zpool was
Thanks for the input Darren, but I'm still confused about DNODE atomicity ...
it's difficult to imagine that a change that is made anyplace in the zpool
would require copy operations all the way back up to the uberblock (e.g. if
some single file in one of many file systems in a zpool was suddenl