On Sun, Jan 06, 2008 at 08:05:56AM -0800, sudarshan sridhar wrote:
> My exact doubt is, if COW is default behavior of ZFS then does COWd
> data written to the same physical drive where the filesystem
> resides?
Just to clarify: there is no way to disable COW in ZFS.
> If so the physical
sudarshan sridhar wrote:
> /Hi,/
> //
> / >>Also where exactly COWed data written
> /
> >>>I'm not quite sure what you're asking here. Data, whether newly
> written or >>>copy-on-write, goes to a newly allocated block, which
> may reside on any >>>vdev, and will be spread across devices if using
sudarshan sridhar wrote:
>> I'm not quite sure what you're asking here. Data, whether newly written or
>> copy-on-write, goes to a newly allocated block, which may reside on any
>> vdev, and will be spread across devices if using RAID.
> My exact doubt is, if COW is default behavior of ZFS then
Hi,
>>Also where exactly COWed data written
>>>I'm not quite sure what you're asking here. Data, whether newly written or
>>copy-on-write, goes to a newly allocated block, which may reside on any
>>vdev, and will be spread across devices if using RAID.
My exact doubt is, if COW
> Does copy-on-write happen every time when any data block of ZFS is getting
> modified?
Yes. (Data block or meta-data block, with the sole exception of the set of
überblocks.)
> Also where exactly COWed data written
I'm not quite sure what you're asking here. Data, whether newly written or
Hi,
Does copy-on-write happens every time when any data block of ZFS is getting
modified? or one needs to configure to enable COW for ZFS while creating?
Also where exactly COWed data written if my storage pool is a single physical
device or even multiple divices are there but used
