Re: ZFS on a notebook/512M settings

5 msg	nmdm(4) does not call .l_close
2 msg	tcp messages I've never seen now in Current and...
2 msg	net/twinkle stuck in _umtx_op syscall
2 msg	Minor miracle
1 msg	emu10kx and related Creative drivers
2 msg	Can't build -current on a 6.2 box
2 msg	setting dumpdev while boot on 7-CURRENT
12 msg	Can't create TCP connections to certain IP addr...
2 msg	snd_emu10k1 mixer

ZFS on a notebook/512M settings
\ Dmitry Morozovsky (25 Jul 2007)
. \ Craig Boston (25 Jul 2007)
. . \ Pawel Jakub Dawidek (26 Jul 2007)
. . . \ Craig Boston (26 Jul 2007)

5 msg	Are SATA port multipliers supported in -CURRENT?
6 msg	installworld breaks my FreeBSD/powerpc system!!!
1 msg	page fault in g_event (probably zfs related?)
8 msg	FreeBSD on intel Mac
5 msg	ZFS on root: slave mountpoints mount failed
2 msg	Call for testers: NetBSD IGMPv2 merge
3 msg	Interrupt storm on atapci1+
4 msg	Error while upgrading FreeBSD-Release6.1 to CUR...
5 msg	Removing NET_NEEDS_GIANT: first patch
5 msg	zsh oddities with recent -current

Subject:	Re: ZFS on a notebook/512M settings
Group:	Freebsd-current
From:	Craig Boston
Date:	26 Jul 2007

On Thu, Jul 26, 2007 at 03:42:31PM +0200, Pawel Jakub Dawidek wrote:
> Let me explain what disabling ZIL really means. Once ZIL is disabled,
> fsync(2) is a no-op, ie. calling fsync(2) on a descriptor doesn't mean
> your data would be safely stored on disk at the time function returns.
> There is no data corruption for local use, only this fsync(2) problem.
>
> "Data corruption" can happen from NFS client point of view, when your
> ZFS file system is exported over NFS and your NFS server crashes.

Does this increase the window after an fsync is performed that a crash
or power loss will lose recent changes? That's what I got from reading
the descriptions of ZIL, perhaps "corruption" was a poor choice of
words.

Craig
_______________________________________________
freebsd-current mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe"