From: Andreas Schwab <schwab@linux-m68k.org>
To: support <support@roosoft.ltd.uk>
Cc: 64588@debbugs.gnu.org,
"debug@roosoft.ltd.uk" <debug@roosoft.ltd.uk>,
"Pádraig Brady" <P@draigBrady.com>
Subject: bug#64588: BUG: stat -f incorrectly reports a BTRFS device as a tmpfs
Date: Thu, 13 Jul 2023 18:02:12 +0200 [thread overview]
Message-ID: <87zg3zajgb.fsf@igel.home> (raw)
In-Reply-To: <550f337c-6561-bf9e-3cb9-38ded4d30683@roosoft.ltd.uk> (support@roosoft.ltd.uk's message of "Thu, 13 Jul 2023 11:33:57 +0100")
On Jul 13 2023, support wrote:
> # function: is_btrfs
> # parameter: path to a mounted filesystem
A device node is not a path to a mounted filesystem
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2023-07-13 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 22:46 bug#64588: BUG: stat -f incorrectly reports a BTRFS device as a tmpfs support
2023-07-13 9:59 ` Pádraig Brady
2023-07-13 10:33 ` support
2023-07-13 12:35 ` Pádraig Brady
2023-07-13 16:02 ` Andreas Schwab [this message]
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
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zg3zajgb.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=64588@debbugs.gnu.org \
--cc=P@draigBrady.com \
--cc=debug@roosoft.ltd.uk \
--cc=support@roosoft.ltd.uk \
/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).