Hello all,
I recently heard an argument from a colleague that ZFS mis-uses
the term COW (Copy-On-Write). According to him, the original term
was introduced by some vendors and was to be taken literally: that
is, whenever a new write comes to update an existing logical block
in the storage, the
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of Jim Klimov
I recently heard an argument from a colleague that ZFS mis-uses
the term COW (Copy-On-Write). According to him, the original term
was introduced by some vendors and was to be
On Tue, Jun 5, 2012 at 6:32 AM, Jim Klimov jimkli...@cos.ru wrote:
I recently heard an argument from a colleague that ZFS mis-uses
the term COW (Copy-On-Write). According to him, the original term
was introduced by some vendors and was to be taken literally: that
is, whenever a new write
COW goes back at least to the early days of virtual memory and fork().
On fork() the kernel would arrange for writable pages in the parent
process to be made read-only so that writes to them could be caught
and then the page fault handler would copy the page (and restore write
access) so the
