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 is default
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
I am trying to understand the ZFS layout from a pdf available on Solaris site.
I have couple of queries related to it.
1. Layout tells root vdev is th main root vdev and other vdevs (physical
and top level vdevs are arranged in a tree format). So is root vdev is a
single entity for whole
Hi bu manzhao,
Thank for you quick response. I have some further queries to your answer
(wirtten with sridhar tag). It would be great if you could provide inputs for
them to understand ZFS better.
ZFS is base in storage pool, and a pool is consist of some vdevs in tree
structure.
I would like to know the method of getting/setting Extended Attributes (EAs)
for files and directoreis.
Also I would like to know is there any difference in getting/setting EAs from
UFS filesystem ?. I mean can we use same system calls, open, openat etc... to
extract EA information?
