From owner-cvs-sys  Tue Nov 12 17:46:11 1996
Return-Path: owner-cvs-sys
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA17568
          for cvs-sys-outgoing; Tue, 12 Nov 1996 17:46:11 -0800 (PST)
Received: (from julian@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA17549;
          Tue, 12 Nov 1996 17:45:59 -0800 (PST)
Date: Tue, 12 Nov 1996 17:45:59 -0800 (PST)
From: Julian Elischer <julian>
Message-Id: <199611130145.RAA17549@freefall.freebsd.org>
To: CVS-committers, cvs-all, cvs-sys
Subject: cvs commit:  src/sys/ufs/ffs ffs_vfsops.c
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

julian      96/11/12 17:45:58

  Modified:    sys/ufs/ffs  ffs_vfsops.c
  Log:
  Submitted by: Archie and me.
  
  We encountered an interesting situation where the superblock for
  a file system got written to disk with the "fs_fmod" flag set to
  one. It appears that this flag is normally supposed to be cleared
  during ffs_sync(), but we experienced a crash, or some other weird
  occurrence that left it on the disk set to 1.
  
  Later this partition was mounted read-only... and the fs_fmod
  field was never cleared, causing ffs_sync() to panic "rofs mod"
  when trying to unmount that filesystem (ffs_vfsops.c: line 790).
  
  fix:
  set this bit to 0 when you load the superblock from disk.
  (see more complete mail on this to hackers)
  
  Revision  Changes    Path
  1.42      +3 -1      src/sys/ufs/ffs/ffs_vfsops.c