Julian Elischer 3f6f17ee1e 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)		1996-11-13 01:45:56 +00:00
..
ffs_alloc.c
ffs_balloc.c
ffs_extern.h
ffs_inode.c	Eliminate an unnecessary synchronous write (and an 8K bcopy+bzero) when	1996-11-05 08:19:40 +00:00
ffs_subr.c
ffs_tables.c
ffs_vfsops.c	Submitted by: Archie and me.	1996-11-13 01:45:56 +00:00
ffs_vnops.c
fs.h