Date: Thu, 26 Oct 2000 18:27:39 +0200 From: Johan Karlsson <k@numeri.campus.luth.se> To: Dmitry Valdov <dv@dv.ru> Cc: current@FreeBSD.ORG Subject: Re: fsck in -current Message-ID: <200010261627.SAA04834@numeri.campus.luth.se> In-Reply-To: Your message of "Thu, 26 Oct 2000 19:23:27 %2B0400." <Pine.BSF.3.95q.1001026191727.7518A-100000@xkis.kis.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
At Thu, 26 Oct 2000 19:23:27 +0400, Dmitry Valdov wrote: > Hello! > > fsck tries to run fsck_msdos for MSDOS partition, but there is no > fsck_msdos in -current. > > > Also fsck(8) says: > SEE ALSO > mount(8), fstab(5), fsck_msdos(8), fsck_ffs(8) > > ... > > man fsck_msdos > No manual entry for fsck_msdos > > > > Dmitry. Hi Adrian sent this HEADS UP to current a while ago: ====== Date: Fri, 13 Oct 2000 17:17:37 +0200 From: Adrian Chadd <adrian@FreeBSD.ORG> To: freebsd-current@FreeBSD.ORG Subject: HEADS UP: fsck wrappers gotcha As pointed out by mr Sobolev, the fsck wrappers will blindly try to execute fsck_$FS regardless of whether its there or not, and fail if it isn't. This is a gotcha for non-fsck'able fses right now, such as nfs and ntfs. The solution, which I forgot to add in my email, is to set pass to 0. This forces fsck to NOT consider the FS for fsck-on-boot, and should make things quieter. Note that swap / procfs in /etc/fstab already use dump/pass = 0, but this is just to make sure. Just FYI, Adrian ======= /Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200010261627.SAA04834>