All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [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":
Date: Sun, 23 Aug 2020 10:07:00 +0000	[thread overview]
Message-ID: <bug-209005-201763@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=209005

            Bug ID: 209005
           Summary: xfs_repair 5.7.0: missing newline in message: entry at
                    block N offset NN in directory inode NNNNNN has
                    illegal name "/foo":
           Product: File System
           Version: 2.5
    Kernel Version: #1 SMP Debian 3.16.59-1 (2018-10-03)
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: XFS
          Assignee: filesystem_xfs@kernel-bugs.kernel.org
          Reporter: cs@cskk.id.au
        Regression: No

Here's an example:

entry at block 0 offset 1728 in directory inode 21997239545 has illegal name
"/gnome-dev-harddisk-1394.png": entry at block 0 offset 1768 in directory inode
21997239545 has illegal name "/gnome-dev-harddisk-usb.png": entry at block 0
offset 1808 in directory inode 21997239545 has illegal name
"/gnome-dev-harddisk.png":

I presume there's a missing newline or some missing trailing message component.

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

             reply	other threads:[~2020-08-23 10:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-23 10:07 bugzilla-daemon [this message]
2020-08-24 17:48 ` [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": 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
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@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.