julian 3781f2dcb0 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	Submitted by: Archie and me.	1996-11-13 01:45:56 +00:00
lfs	Whoops, I should've used the LINT config file. More ts -> tv changes	1996-09-20 05:56:36 +00:00
mfs	struct mfsnode bloated in size by 12 bytes, so reduce spare padding by 3 longs.	1996-11-04 20:53:02 +00:00
ufs	Fixed some races and misleading comments in ufs_rename().	1996-11-04 16:05:51 +00:00