From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 217769] XFS crash on mount on kernels >= 6.1
Date: Mon, 07 Aug 2023 19:01:09 +0000 [thread overview]
Message-ID: <bug-217769-201763-rlUaC4Qyh7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217769-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217769
--- Comment #3 from Eric Sandeen (sandeen@sandeen.net) ---
It's essentially an unexpected/inconsistent in-memory state, as opposed to an
on-disk structure that was found to be corrupt.
I presume that it boots ok now post-repair?
Do you know if this was the root or /boot filesystem or something else? It's
still a mystery about how filesystems get into this state; we should never have
a clean filesystem that requires no log recovery, but with unlinked inodes ...
recovery is supposed to clear that.
It may have persisted on this filesystem for a very long time and it's just
recent code changes that have started tripping over it, but I've always had a
hunch that /boot seems to show the problem more often.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-08-07 19:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 16:35 [Bug 217769] New: XFS crash on mount on kernels >= 6.1 bugzilla-daemon
2023-08-07 17:17 ` [Bug 217769] " bugzilla-daemon
2023-08-07 18:06 ` bugzilla-daemon
2023-08-07 19:01 ` bugzilla-daemon [this message]
2023-08-07 19:40 ` bugzilla-daemon
2023-08-07 20:15 ` bugzilla-daemon
2023-08-07 22:34 ` bugzilla-daemon
2023-08-08 13:39 ` bugzilla-daemon
2023-08-08 14:51 ` bugzilla-daemon
2023-08-08 14:54 ` bugzilla-daemon
2023-08-08 14:55 ` bugzilla-daemon
2023-08-08 21:54 ` bugzilla-daemon
2023-08-08 22:07 ` bugzilla-daemon
2023-08-09 16:43 ` bugzilla-daemon
2023-08-09 18:31 ` bugzilla-daemon
2023-08-09 19:10 ` bugzilla-daemon
2023-08-29 23:42 ` Darrick J. Wong
2023-08-29 23:42 ` bugzilla-daemon
2023-11-14 15:57 ` bugzilla-daemon
2023-11-14 23:46 ` Darrick J. Wong
2023-11-14 23:46 ` bugzilla-daemon
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=bug-217769-201763-rlUaC4Qyh7@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-xfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.