Date: Mon, 31 Jul 2006 03:22:42 -0700 (PDT) From: "R. B. Riddick" <arne_woerner@yahoo.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: Brent Hostetler <brenthostetler@gmail.com>, freebsd-geom@freebsd.org Subject: Re: gmirror/gconcat: mkdir causes system reboot Message-ID: <20060731102242.41080.qmail@web30305.mail.mud.yahoo.com> In-Reply-To: <20060731101033.GA842@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Pawel Jakub Dawidek <pjd@FreeBSD.org> wrote: > Gmirror protects against such situations - on power loss or system crash > it will resynchronize mirrors. > Hmm... The evil is a squirrel... E. g. the write cache could delay the commit regarding the last sector of the disc until the data has been written... Then the sudden power loss (or so) could happen, while one disc updates the data but before the other disc and the meta data are written. Or not? Or is gmirror like gjournal? In graid5 I mark the geom_device as clean as soon as the shutdown event occurs. Is that a good idea? That makes versioning of the various disks obsolete, doesn't it? -Arne __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060731102242.41080.qmail>