From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 218764] New: xfs_scrub_all.in: NameError: name 'path' is not defined
Date: Tue, 23 Apr 2024 03:24:32 +0000 [thread overview]
Message-ID: <bug-218764-201763@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=218764
Bug ID: 218764
Summary: xfs_scrub_all.in: NameError: name 'path' is not
defined
Product: File System
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: XFS
Assignee: filesystem_xfs@kernel-bugs.kernel.org
Reporter: 60510scott@gmail.com
Regression: No
Created attachment 306198
--> https://bugzilla.kernel.org/attachment.cgi?id=306198&action=edit
journalctl -b -u xfs_scrub_all.service
`path` variable is not defined in
https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/tree/scrub/xfs_scrub_all.in#n166
Attached is the error log of `xfs_scrub_all.service`
--
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 reply other threads:[~2024-04-23 3:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 3:24 bugzilla-daemon [this message]
2024-04-24 3:39 ` [Bug 218764] New: xfs_scrub_all.in: NameError: name 'path' is not defined Darrick J. Wong
2024-04-24 3:39 ` [Bug 218764] " 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-218764-201763@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).