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_alloc.c

Argh, I have had one "uid 0 on /: file system full" too many. The problem

1996-09-17 14:38:16 +00:00

ffs_balloc.c

Eliminated many redundant vm_map_lookup operations for vm_mmap.

1996-01-19 04:00:31 +00:00

ffs_extern.h

Removed bogus _BEGIN_DECLS/_END_DECLS.

1996-05-01 02:16:17 +00:00

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

Convert DDB to new-style option.

1996-01-04 21:13:23 +00:00

ffs_tables.c

Staticize.

1995-12-17 21:14:36 +00:00

ffs_vfsops.c

Submitted by: Archie and me.

1996-11-13 01:45:56 +00:00

ffs_vnops.c

Staticize.

1995-12-17 21:14:36 +00:00

fs.h

Fixed lblktosize(). It overflowed at 2G. This bug only affected

1996-10-12 22:12:51 +00:00