From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 209005] xfs_repair 5.7.0: missing newline in message: entry at block N offset NN in directory inode NNNNNN has illegal name "/foo":
Date: Mon, 24 Aug 2020 21:03:40 +0000 [thread overview]
Message-ID: <bug-209005-201763-njhnZyhZxR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209005-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209005
--- Comment #3 from Eric Sandeen (sandeen@redhat.com) ---
IOWs this looks like more than just a missing "\n" - setting the first
character of a directory entry to "/" is an internal flag for certain entries
which is normally handled in a specific way.
But it doesn't look like your filenames are overwritten; it looks like they
actually started with "/" prior to repair? So it may not be handling this
flagging properly when the leading "/" came from elsewhere... a metadump would
be helpful.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-08-24 21:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 10:07 [Bug 209005] New: xfs_repair 5.7.0: missing newline in message: entry at block N offset NN in directory inode NNNNNN has illegal name "/foo": bugzilla-daemon
2020-08-24 17:48 ` [Bug 209005] " bugzilla-daemon
2020-08-24 17:49 ` bugzilla-daemon
2020-08-24 21:03 ` bugzilla-daemon [this message]
2020-08-24 21:29 ` bugzilla-daemon
2020-08-24 21:49 ` bugzilla-daemon
2020-08-24 22:27 ` bugzilla-daemon
2020-08-24 22:35 ` bugzilla-daemon
2020-08-24 22:48 ` 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-209005-201763-njhnZyhZxR@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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.