Date: Fri, 08 Apr 2011 15:11:01 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Garrett Cooper <yanegomi@gmail.com> Cc: freebsd-fs@FreeBSD.org, FreeBSD Hackers <freebsd-hackers@FreeBSD.org> Subject: Re: retry mounting with ro when rw fails Message-ID: <4D9EFB55.1000706@FreeBSD.org> In-Reply-To: <BANLkTimAyh4-T0gQ1cuQn0nm8m7SHwW5iA@mail.gmail.com> References: <4D9DF375.4080506@FreeBSD.org> <BANLkTimAyh4-T0gQ1cuQn0nm8m7SHwW5iA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 07/04/2011 23:20 Garrett Cooper said the following: > > As a generic question / observation, maybe we should just > implement 'errors=remount-ro' (or a reasonable facsimile) like Linux > has in our mount(8) command? Doesn't look like NetBSD, OpenBSD, or > [Open]Solaris sported similar functionality. No problem, I am OK with being first. Then, I only want to deal with media that is "semi-permanently" or permanetly read-only. That's why I handle only failure to mount media as R/W. But from what I read 'errors=remount-ro' in Linux has to do with errors that happen after filesystem is mounted. That is, you mounted a filesystem, you work with it, you get some error (e.g. because of bad blocks), you auto-downgrade the filesystem to readonly. This may be a nice feature, but this is something different from what I proposed. And, AFAIK, Linux does what I propose by default, without any additional options. Google for "block device ... is write-protected, mounting read-only". But yes, it seems that they handle this situation entirely in userland. And I am not against it. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D9EFB55.1000706>