From: Roman Mamedov <rm@romanrm.net>
To: Lawrence D'Anna <larry@elder-gods.org>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
Meghan Gwyer <mgwyer@gmail.com>
Subject: Re: bizare bug in "btrfs subvolume show"
Date: Sun, 15 Nov 2020 14:53:23 +0500 [thread overview]
Message-ID: <20201115145323.1628d710@natsu> (raw)
In-Reply-To: <8EFE06A3-9CC4-4A6A-850F-C7C57DC27942@elder-gods.org>
On Sat, 14 Nov 2020 13:35:43 -0800
Lawrence D'Anna <larry@elder-gods.org> wrote:
> > On Nov 13, 2020, at 9:47 PM, Lawrence D'Anna <larry@elder-gods.org> wrote:
> >
> >
> > But I haven’t been able to track down how redirecting the standard out is possibly influencing this.
>
> I have narrowed it down a little bit further.
>
> cmd_subvol_show uses btrfs_util_subvolume_iterator_next_info to find all the snapshots of the
> subvol it’s showing.
>
> while it’s performing this iteration, subvolume_iterator_next_tree_search returns a subvolume id
> of 7168, which does not appear in my filesystem according to "btrfs subvol list”
This still sounds very puzzling, as to how output redirection could affect
things. Perhaps you could run "btrfs sub show" with "strace"? Both with and
without the redirect to see exactly what was the call sequence, parameters and
return values, to compare and find where the difference starts.
--
With respect,
Roman
next prev parent reply other threads:[~2020-11-15 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 5:47 bizare bug in "btrfs subvolume show" Lawrence D'Anna
2020-11-14 7:28 ` Chris Murphy
2020-11-14 18:29 ` Lawrence D'Anna
2020-11-14 21:35 ` Lawrence D'Anna
2020-11-15 9:53 ` Roman Mamedov [this message]
2020-11-16 2:09 ` Lawrence D'Anna
2020-11-16 20:31 ` Goffredo Baroncelli
2020-11-16 20:51 ` Lawrence D'Anna
2020-11-18 1:17 ` Lawrence D'Anna
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=20201115145323.1628d710@natsu \
--to=rm@romanrm.net \
--cc=larry@elder-gods.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=mgwyer@gmail.com \
/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