public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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 22:27:19 +0000	[thread overview]
Message-ID: <bug-209005-201763-v25JDTo37q@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 #6 from Cameron Simpson (cs@cskk.id.au) ---
Sorry for the delay, been asleep.

Alas, the filesystem has been repaired and I didn't keep a log, or alas, a
transcript.

The xfs_repair is from xfsprogs 5.7.0.

By contrast, the filesystem is made by quite an old kernel:

Linux octopus 3.16.0-7-amd64 #1 SMP Debian 3.16.59-1 (2018-10-03) x86_64
GNU/Linux

and I have seen this filenames-with-a-leading-slash in a previous repair of an
XFS filesystem from this machine.

This bug report is really about the messaging, not the bogus filenames; I
accept that the kernel is old and the XFS implementation therefore many
bugfixes behind.

For added fun the FS is on an iscsi device from a QNAP NAS (because QNAPs don't
do XFS); I started the repair after getting link errors on the FS, after a
building wide power out took out the machine and the NAS; and we had to reseat
a drive in the raidset. It's just backups, but it has 5TB of highly linked
files in it.

Just FYI, BTW, a second run of xfs_repair after the big repair corrected a few
hardlink counts (but a mere handful, maybe 4, after the previous repair did
thousands of fixes).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-08-24 22:27 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
2020-08-24 21:29 ` bugzilla-daemon
2020-08-24 21:49 ` bugzilla-daemon
2020-08-24 22:27 ` bugzilla-daemon [this message]
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-v25JDTo37q@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox