There is no clustering package for it and available source seems very old also
the de-dup bug is there iirc. So if you don't need HA cluster and dedup..
BR, Jeffry
-Original Message-
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of
Thx all, I understand now.
BR, Jeffry
if an application requests a synchronous write then it is commited to
ZIL immediately, once it is done the IO is acknowledged to application.
But data written to ZIL is still in memory as part of an currently open
txg and will be committed to a pool
Sometimes people get confused about the ZIL and separate logs. For
sizing purposes,
the ZIL is a write-only workload. Data which is written to the ZIL is
later asynchronously
written to the pool when the txg is committed.
Right; the tgx needs time to transfer the ZIL.
The ZFS write
-Original Message-
From: neil.per...@sun.com [mailto:neil.per...@sun.com]
I think you misunderstand the function of the ZIL. It's not a journal,
and doesn't get transferred to the pool as of a txg. It's only ever
written except
after a crash it's read to do replay. See:
Hi all,
Are there any recommendations regarding min IOPS the backing storage pool needs
to have when flushing the SSD ZIL to the pool? Consider a pool of 3x 2TB SATA
disks in RAIZ1, you would roughly have 80 IOPS. Any info about the relation
between ZIL pool performance? Or will the ZIL
There are different kinds of IOPS. The expensive ones are random
IOPS whereas sequential IOPS are much more efficient. The intention
of the SSD-based ZIL is to defer the physical write so that would-be
random IOPS can be converted to sequential scheduled IOPS like a
normal write. ZFS
Actually, I asked about this a while ago only called it file-level cloning.
Consider you have 100VM's and you want to clone just one?
BTRFS added a specialized IOCTL() call to make the FS aware that it has to
clone this obviously saves copy time and dedup time.
Regards, Jeffry
In my experience, cloning is done for basic provisioning, so how would
you get
to the case where you could not clone any particular VM?
-- richard
Well, a situation where this might come in handy is when you have your typical
ISP provider that has multiple ESX hosts with multiple
Agreed, but still: wy zpool iostat 15MB en iostat 615KB?
Regard, Jeff
From: zfs-discuss-boun...@opensolaris.org [zfs-discuss-boun...@opensolaris.org]
On Behalf Of Bob Friesenhahn [bfrie...@simple.dallas.tx.us]
Sent: Friday, November 13, 2009 4:05 PM
To:
Yes but the number of nfs mounts/datastores for ESX is limited; so that would
leave me with limited numer of clones.
Jeff
From: Robert Milkowski [mi...@task.gda.pl]
Sent: Friday, October 30, 2009 2:31 AM
To: Jeffry Molanus
Cc: zfs-discuss
Hi all,
Does zfs/solaris provide a easy way to clone at file level? I.e clone a large
vmdk?
Regards, jeff
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
: Jeffry Molanus
Onderwerp: Re: [zfs-discuss] File level cloning
What are you doing with your vmdk file(s) from the clone?
On 10/28/09 9:36 AM, Jeffry Molanus jeffry.mola...@proact.nl wrote:
Agreed, but with file level it is more granular then cloning a whole fs
and I
would not need to delete
12 matches
Mail list logo
