public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: Does OpenRC really need mount-ro
Date: Tue, 16 Feb 2016 13:22:13 -0500	[thread overview]
Message-ID: <CAGfcS_mus8xykkCSd+WXZmx68SABa6AJXHKvKSao77WMbVH9sw@mail.gmail.com> (raw)
In-Reply-To: <20160216180533.GB1450@whubbs1.gaikai.biz>

On Tue, Feb 16, 2016 at 1:05 PM, William Hubbs <williamh@gentoo.org> wrote:
>
> The reason it exists is very vague to me; I think it has something to do
> with claims of data loss in the past.
>

Is there some other event that will cause all filesystems to be
remounted read-only or unmounted before shutdown?

You definitely will want to either unmount or remount readonly all
filesystems prior to rebooting.  I don't think the kernel guarantees
that this will happen (I'd have to look at it).  Just doing a sync
before poweroff doesn't seem ideal - if nothing else it will leave
filesystems marked as dirty and likely force fscks on the next boot
(or at least it should - if it doesn't that is another opportunity for
data loss).

There are different ways of accomplishing this of course, but you
really want to have everything read-only in the end.

-- 
Rich


  reply	other threads:[~2016-02-16 18:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 18:05 [gentoo-dev] rfc: Does OpenRC really need mount-ro William Hubbs
2016-02-16 18:22 ` Rich Freeman [this message]
2016-02-16 18:41   ` William Hubbs
2016-02-17  2:20     ` [gentoo-dev] " Duncan
2016-02-17 13:46       ` Rich Freeman
2016-02-18  8:57         ` Duncan
2016-02-18 12:22           ` Rich Freeman
2016-02-19  5:07             ` Duncan
2016-02-25 23:46               ` Raymond Jennings
2016-02-17 14:24       ` Richard Yao
2016-02-17 17:19         ` Rich Freeman
2016-02-17 17:30           ` James Le Cuirot
2016-02-17 18:06             ` Ian Stakenvicius
2016-02-17 18:32               ` Rich Freeman
2016-02-18  3:11                 ` Richard Yao
2016-02-18  9:02                   ` James Le Cuirot
2016-02-18 11:39                   ` Rich Freeman
2016-02-17 21:50             ` Daniel Campbell
2016-02-18  3:02           ` Richard Yao
2016-02-18 10:48             ` Rich Freeman
2016-02-17 14:05     ` [gentoo-dev] " Richard Yao
2016-02-16 19:31 ` Patrick Lauer
2016-02-16 20:18   ` Rich Freeman
2016-02-17 14:06     ` Richard Yao
2016-02-17 19:01     ` Andrew Savchenko
2016-02-17 19:26       ` Rich Freeman
2016-02-18  3:26       ` Richard Yao
2016-02-18  7:53         ` Andrew Savchenko
2016-02-16 20:03 ` Daniel Campbell
2016-02-17  8:24 ` Luca Barbato
2016-02-17 14:00 ` Richard Yao
2016-02-18  7:02 ` Robin H. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGfcS_mus8xykkCSd+WXZmx68SABa6AJXHKvKSao77WMbVH9sw@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox