Date: Thu, 29 Nov 2018 03:08:36 +1100 (EST) From: Bruce Evans <brde@optusnet.com.au> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: Kirk McKusick <mckusick@mckusick.com>, FreeBSD FS <freebsd-fs@freebsd.org>, "Julian H. Stacey" <jhs@berklix.com>, "soralx@cydem.org" <soralx@cydem.org> Subject: Re: [bug] fsck refuses to repair damaged UFS using backup superblock Message-ID: <20181129030116.W3915@besplex.bde.org> In-Reply-To: <YTOPR0101MB11621E634B328D96D1B1B123DDD10@YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM> References: <YTOPR0101MB11624C6EA47C4AA2F14945A1DDD10@YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM>, <201811280759.wAS7xabP040527@chez.mckusick.com> <YTOPR0101MB11621E634B328D96D1B1B123DDD10@YTOPR0101MB1162.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 28 Nov 2018, Rick Macklem wrote: > Kirk McKusick wrote: > [stuff snipped] > I wrote: >>> >>> For booting, I think Warner is correct to suggest "print a warning >>> and soldier on..". However, once the system has booted (maybe only >>> single user), I'd think it would be better to fail the mount at >>> least until an fsck is done on it than allow it to be mounted >>> read-only, unless there is no risk that doing this mount could cause >>> a crash/panic. > Oops, I realize I missed a key phrase in the above (run on) sentence. > The key phrase was "for file systems other than root". > > I was basically trying to say what bde@ said. I noticed after replying that I repeated what you said in a paragraph that I didn't read closely and didn't quote. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181129030116.W3915>