Re: kern/47231 (crash or power loss during cvs update on WAPBL-enabled volume results in near-irreparable damage to CVS metadata.)

[David Laight <david%l8s.co.uk@localhost>]

The following reply was made to PR kern/47231; it has been noted by GNATS.

From: David Laight <david%l8s.co.uk@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
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 08:27:32 +0000

 On Wed, Nov 28, 2012 at 03:30:10PM +0000, dholland%NetBSD.org@localhost wrote:
 > Synopsis: crash or power loss during cvs update on WAPBL-enabled volume 
 > results in near-irreparable damage to CVS metadata.
 
 Is this the 'problem' that is caused by cvs doing the 'safe' sequence
 of writing a new CVS/Entries file and then renaming it to replace the
 old one?
 
 After a crash all the directory and inode information is correct,
 but the disk blocks backing the files have not been rewritten?
 
 The effect being that most of the CVS/Entries files contain the
 contents of the files for other directories!
 
 I got an fs into that mess after a cvs diff (which also seems to
 rewrite the Entries files) - but I might have had it mounted async.
 
        David
 
 -- 
 David Laight: david%l8s.co.uk@localhost