Date: Sun, 06 May 2007 03:04:23 +0200 From: Ivan Voras <ivoras@fer.hr> To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= <des@des.no> Cc: freebsd-geom@freebsd.org Subject: Re: graid5 after-reboot problem Message-ID: <463D2997.2050207@fer.hr> In-Reply-To: <86fy6bqocr.fsf@dwp.des.no> References: <171980743.20070504223126@uzvik.kiev.ua> <125507.38194.qm@web30304.mail.mud.yahoo.com> <f1i3s4$j4n$1@sea.gmane.org> <86fy6bqocr.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB051F796716AD8B02D55F406 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dag-Erling Sm=C3=B8rgrav wrote: > Ivan Voras <ivoras@fer.hr> writes: >> Is the write cache in graid5 aware of what happens on the VFS / UFS >> layers (something like gjournal does)? Otherwise, how can you guarante= e >> consistency with write caching at the GEOM layer when there's a power >> outage or some other system interruption? >=20 > You can't. Google for "RAID 5 write hole" for an explanation. It was a rhetorical question :) --------------enigB051F796716AD8B02D55F406 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGPSmXldnAQVacBcgRAgk6AKCfoUPOm1TmzicxoGEE5LsgRCNcVQCgtLyh 7EfkINylR0hIyhjrtsGpIVU= =ky+m -----END PGP SIGNATURE----- --------------enigB051F796716AD8B02D55F406--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?463D2997.2050207>