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
Hi all,
Two questions from a newbie.
1/ What REFER mean in zfs list ?
2/ How can I known the size of all snapshot size for a partition ?
(OK I can add zfs list -t snapshot)
Regards.
JAS
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
Two questions from a newbie.
1/ What REFER mean in zfs list ?
The amount of data that is reachable from the file system root. It's
just what I would call the contents of the file system.
2/ How can I known the size of all snapshot size for a partition ?
(OK I can add
Le 05/06/2012 ? 17:08:51+0200, Stefan Ring a écrit
Two questions from a newbie.
1/ What REFER mean in zfs list ?
The amount of data that is reachable from the file system root. It's
just what I would call the contents of the file system.
OK thanks.
2/ How can I
Can I say
USED-REFER=snapshot size ?
No. USED is the space that would be freed if you destroyed the
snapshot _right now_. This can change (and usually does) if you
destroy previous snapshots.
___
zfs-discuss mailing list
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
