What you say is true only on the system itself. On an NFS client system, 30
seconds of lost data in the middle of a file (as per my earlier example) is a
corrupt file.
-original message-
Subject: Re: [zfs-discuss] Solaris startup script location
From: Edward Ned Harvey
Date: 18/08/2010 17:17
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Alxen4
>
> For example I'm trying to use ramdisk as ZIL device (ramdiskadm )
Other people have already corrected you about ramdisk for log.
It's already been said, use SSD, or disable ZIL comp
> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Alxen4
>
> Disabling ZIL converts all synchronous calls to asynchronous which
> makes ZSF to report data acknowledgment before it actually was written
> to stable storage which in turn improves
On Wed, Aug 18, 2010 at 12:16:04AM -0700, Alxen4 wrote:
> Is there any way run start-up script before non-root pool is mounted ?
>
> For example I'm trying to use ramdisk as ZIL device (ramdiskadm )
> So I need to create ramdisk before actual pool is mounted otherwise it
> complains that log devi
Il giorno 18/ago/2010, alle ore 10.20, Alxen4 ha scritto:
> My NFS Client is ESXi so the major question is there risk of corruption for
> VMware images if I disable ZIL ?
I do the same use of ZFS. I had a huge improvement in performance by using
mirrors instead of raidz. How is your zpool confi
Thanks.Everything is clear now.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Wed, 2010-08-18 at 01:20 -0700, Alxen4 wrote:
> Thanks...Now I think I understand...
>
> Let me summarize it andd let me know if I'm wrong.
>
> Disabling ZIL converts all synchronous calls to asynchronous which makes ZSF
> to report data acknowledgment before it actually was written to stable
Alxen4 wrote:
Thanks...Now I think I understand...
Let me summarize it andd let me know if I'm wrong.
Disabling ZIL converts all synchronous calls to asynchronous which makes ZSF to
report data acknowledgment before it actually was written to stable storage
which in turn improves performance
Thanks...Now I think I understand...
Let me summarize it andd let me know if I'm wrong.
Disabling ZIL converts all synchronous calls to asynchronous which makes ZSF to
report data acknowledgment before it actually was written to stable storage
which in turn improves performance but might cause
Andrew Gabriel wrote:
Alxen4 wrote:
Is there any way run start-up script before non-root pool is mounted ?
For example I'm trying to use ramdisk as ZIL device (ramdiskadm )
So I need to create ramdisk before actual pool is mounted otherwise
it complains that log device is missing :)
For sure
On Wed, 2010-08-18 at 00:49 -0700, Alxen4 wrote:
> Any argumentation why ?
Because a RAMDISK defeats the purpose of a ZIL, which is to provide a
fast *stable storage* for data being written. If you are using a
RAMDISK, you are not getting any non-volatility guarantees that the ZIL
is supposed to
Any argumentation why ?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Alxen4 wrote:
Is there any way run start-up script before non-root pool is mounted ?
For example I'm trying to use ramdisk as ZIL device (ramdiskadm )
So I need to create ramdisk before actual pool is mounted otherwise it
complains that log device is missing :)
For sure I can manually remove/a
On Wed, 2010-08-18 at 00:16 -0700, Alxen4 wrote:
> Is there any way run start-up script before non-root pool is mounted ?
>
> For example I'm trying to use ramdisk as ZIL device (ramdiskadm )
> So I need to create ramdisk before actual pool is mounted otherwise it
> complains that log device is m
Is there any way run start-up script before non-root pool is mounted ?
For example I'm trying to use ramdisk as ZIL device (ramdiskadm )
So I need to create ramdisk before actual pool is mounted otherwise it
complains that log device is missing :)
For sure I can manually remove/and add it by sc
15 matches
Mail list logo
