From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 201823] inconsistent behaviour of xfs_db, xfs_repair and xfs_scrub
Date: Sun, 02 Dec 2018 17:40:05 +0000 [thread overview]
Message-ID: <bug-201823-201763-yOloQjgTGA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201823-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201823
--- Comment #6 from matthias@bodenbinder.de ---
Am 02.12.18 um 18:02 schrieb bugzilla-daemon@bugzilla.kernel.org:
> https://bugzilla.kernel.org/show_bug.cgi?id=201823
>
> --- Comment #5 from Eric Sandeen (sandeen@sandeen.net) ---
> If you'd like to send me a compressed metadump image (offline for maximum
> privacy) I'll take a look.
>
> However, some of your messages above are a result user error: you are
> providing
> a block number as an inode number to xfs_db, so it is trying to parse a
> non-inode as an inode.
>
I will send you a dropbox link to the metadump
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2018-12-02 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 8:16 [Bug 201823] New: inconsistent behaviour of xfs_db, xfs_repair and xfs_scrub bugzilla-daemon
2018-12-01 19:13 ` [Bug 201823] " bugzilla-daemon
2018-12-01 22:44 ` [Bug 201823] New: " Dave Chinner
2018-12-01 22:44 ` [Bug 201823] " bugzilla-daemon
2018-12-02 1:14 ` bugzilla-daemon
2018-12-02 8:27 ` bugzilla-daemon
2018-12-02 17:02 ` bugzilla-daemon
2018-12-02 17:28 ` Matthias Bodenbinder
2018-12-02 17:40 ` bugzilla-daemon [this message]
2018-12-03 21:21 ` bugzilla-daemon
2018-12-03 22:16 ` bugzilla-daemon
2018-12-03 22:35 ` 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-201823-201763-yOloQjgTGA@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