From owner-cvs-contrib  Fri Jun 12 13:54:01 1998
Return-Path: <owner-cvs-contrib>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA11425
          for cvs-contrib-outgoing; Fri, 12 Jun 1998 13:54:01 -0700 (PDT)
          (envelope-from owner-cvs-contrib)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10577;
          Fri, 12 Jun 1998 13:49:01 -0700 (PDT)
          (envelope-from julian@FreeBSD.org)
From: Julian Elischer <julian@FreeBSD.ORG>
Received: (from julian@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id NAA23091;
	Fri, 12 Jun 1998 13:48:34 -0700 (PDT)
Date: Fri, 12 Jun 1998 13:48:34 -0700 (PDT)
Message-Id: <199806122048.NAA23091@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-contrib@FreeBSD.ORG
Subject: cvs commit: src/contrib/sys/softupdates ffs_softdep.c
Sender: owner-cvs-contrib@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

julian      1998/06/12 13:48:33 PDT

  Modified files:
    contrib/sys/softupdates ffs_softdep.c 
  Log:
  Fix the case when renaming to a file that you've just created and deleted,
  that had an inode that has not yet been written to disk, when the inode of the
  new file is also not yet written to disk, and your old directory entry is not
  yet on disk but you need to remove it and the new name exists in memory
  but has been deleted but the transaction to write the deleted name to disk
  exists and has not yet been cancelled by the request to delete the non
  existant name.  I don't know how kirk could have missed such a glaring
  problem for so long. :-) Especially since the inconsitency survived on
  the disk for a whole 4 second on average before being fixed by other code.
  This was not a crashing bug but just led to filesystem inconsitencies
  if you crashed.
  
  Submitted by: Kirk McKusick (mckusick@mckusick.com)
  
  Revision  Changes    Path
  1.11      +43 -22    src/contrib/sys/softupdates/ffs_softdep.c