Date: Sun, 20 Jun 2021 13:19:42 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyNTY3MTJdIFVGUzoga2VybmVsIHBhbmljOiBmZnNfYmxr?= =?UTF-8?B?ZnJlZV9jZzogZnJlZWluZyBmcmVlIGZyYWcg4oCTIGluIHJlc3BvbnNlIHRv?= =?UTF-8?B?IHBrZy1kZWxldGUoOCkgc29vbiBhZnRlciBsb2dpbg==?= Message-ID: <bug-256712-3630-dPIKD650Wo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256712-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-256712-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256712 --- Comment #8 from andrew@tao11.riddles.org.uk --- Incidentally, background fsck (for SU without journalling) seems to have be= en broken for 6 months; commit 5cc52631b3b88 breaks it by trying to open the device for writing when invoked with -B -p as rc.d/bgfsck does. Result is a= "NO WRITE ACCESS" error in the log and no fsck happens. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256712-3630-dPIKD650Wo>