[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/47231: crash or power loss during cvs update on WAPBL-enabled volume results in near-irreparable damage to CVS metadata.
The following reply was made to PR kern/47231; it has been noted by GNATS.
From: "J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost>
Subject: Re: kern/47231: crash or power loss during cvs update on WAPBL-enabled
volume results in near-irreparable damage to CVS metadata.
Date: Thu, 29 Nov 2012 17:13:28 +0100
On Nov 28, 2012, at 4:40 PM, David Holland
> As discussed periodically elsewhere, this is a long-standing design
> bug in ffs (the original motivation for softupdates) which WAPBL fails
> to correct. Experience so far seems to indicate that the problem is
> more severe in practice with WAPBL, probably because it runs faster
> and more data is buffered and unwritten at crash time.
Should we enforce some kind of fsync-on-close on WAPBL enabled fs?
This way at least the common open-write-close-rename sequence should
survive a crash so either the old file or the new one has valid data.
J. Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig
Main Index |
Thread Index |