From: Randy Dunlap <rdunlap@infradead.org>
To: Eric Sandeen <sandeen@redhat.com>,
linux-ext4@vger.kernel.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: ext4 confusion
Date: Mon, 5 Mar 2018 21:12:03 -0800 [thread overview]
Message-ID: <22af62e2-81c7-ad6a-07bd-a05c42ba003a@infradead.org> (raw)
In-Reply-To: <6d0480b3-e201-bdad-3880-103a1fb93c7f@redhat.com>
On 03/05/2018 08:45 PM, Eric Sandeen wrote:
> On 3/5/18 10:42 PM, Randy Dunlap wrote:
>>>> It's a new OS/installer. OpenSUSE Tumbleweed, which is their bleeding edge
>>>> rolling updates release.
>>> Hrmph. A lot of things go into this behavior, it may not be a kernel change at
>>> all that has made it show up now...
>> Yes, it could be that wonderful systemd or something else.
>
> I think I'd pursue a parallel track of bugging SUSE about the issue... ;)
>
> (I don't think the kernel will ever just downgrade an rw mount request to
> ro, or skip an ro->rw transition silently... leaving it ro does seem
> like an init bug, but *shrug* init long ago transitioned into deep magic.)
More info: :(
This problem happens when booting my own custom 4.16-rc3 kernel.
If I boot the OpenSUSE-supplied (4.15.7) kernel, the / fs is remounted rw later on.
So I'm more or less back to "what am I doing wrong"?
thanks,
--
~Randy
next prev parent reply other threads:[~2018-03-06 5:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 4:17 ext4 confusion Randy Dunlap
2018-03-06 4:34 ` Eric Sandeen
2018-03-06 4:38 ` Randy Dunlap
2018-03-06 4:40 ` Eric Sandeen
2018-03-06 4:42 ` Randy Dunlap
2018-03-06 4:45 ` Eric Sandeen
2018-03-06 5:12 ` Randy Dunlap [this message]
2018-03-06 6:47 ` Dave Chinner
2018-03-06 20:07 ` Randy Dunlap
2018-03-06 22:53 ` Eric Sandeen
2018-03-06 22:34 ` Theodore Y. Ts'o
2018-03-06 23:34 ` Randy Dunlap
2018-03-07 4:58 ` Theodore Y. Ts'o
2018-03-07 5:35 ` Randy Dunlap
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=22af62e2-81c7-ad6a-07bd-a05c42ba003a@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).