Re: ext4: spurious "orphan cleanup on readonly fs" due to remount,ro failing to reset orphan_file structures

Jan Kara <[email protected]> Mon, 3 Aug 2026 17:14:29 +0200
Newsgroups org.kernel.vger.linux-ext4,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-kernel
Message-ID <g7fk4a4rsokzzficx63yqcjwbyneq7ipfhshvi5xhylihetjrd@d6sv5y6kwnzs>
On Mon 03-08-26 13:57:55, Tigran Aivazian wrote:
> Hi,
> 
> On Mon, 3 Aug 2026 at 13:36, Jan Kara <[email protected]> wrote:
> > No need to, the behavior didn't change for a long time. In fact, any
> > read-only mount with orphan_file feature enabled will result in the
> > spurious "orphan cleanup on readonly fs" message. I've just checked that.
> > It is only a cosmetic problem but nobody noticed so far.
> 
> You say it is a cosmetic problem, but here I somewhat disagree.
> Logically, seeing "orphan cleanup on readonly fs" implies an unclean
> shutdown that caused those orphans. Consequently, I spent time
> debugging it by instrumenting scripts in
> /usr/lib/systemd/system-shutdown/ and even suspecting the NVMe
> controller caches, etc. Any sysadmin who doesn't like leaving
> "mysteries" on their Linux host would have done the same.

Fair point and to be clear I think this needs to fixed. I can see how this
"cosmetic problem" misled you and you have wasted time debugging that. I'm
sorry for that.

								Honza
-- 
Jan Kara <[email protected]>
SUSE Labs, CR