Kirk McKusick c094263a24 When running fsck_ffs manually, do not ask: ... USE JOURNAL? [yn] when the journal timestamp does not match the filesystem mount time as we are just going to print an error and fall through to a full fsck. Instead, just run a full fsck. Requested by: Bjoern A. Zeeb (bz) MFC after: 7 days		2019-12-24 23:03:12 +00:00
..
dir.c	This revision began as a simple change to eliminate an uninitialized warning	2019-05-21 22:24:38 +00:00
ea.c
fsck_ffs.8	Correct the location of the first backup superblock in fsck_ffs.8.	2019-08-07 16:56:00 +00:00
fsck.h	This update eliminates a kernel stack disclosure bug in UFS/FFS	2019-05-03 21:54:14 +00:00
fsutil.c
gjournal.c
globs.c	This update eliminates a kernel stack disclosure bug in UFS/FFS	2019-05-03 21:54:14 +00:00
inode.c	Followup to -r344552 in which fsck_ffs checks for a size past the	2019-04-13 13:31:06 +00:00
main.c	When running fsck_ffs manually, do not ask:	2019-12-24 23:03:12 +00:00
Makefile
Makefile.depend
pass1.c	Treat any inode with bad content as unknown (i.e., ask if it should	2019-07-20 21:39:32 +00:00
pass1b.c
pass2.c
pass3.c
pass4.c
pass5.c
setup.c	fsck_ffs: fix some memory leaks found by Coverity.	2019-12-10 20:04:08 +00:00
suj.c	When running fsck_ffs manually, do not ask:	2019-12-24 23:03:12 +00:00
utilities.c	Remove unused includes.	2019-12-22 05:44:29 +00:00