From: Petr Vorel <pvorel@suse.cz>
To: Thomas Bertschinger <tahbertschinger@gmail.com>
Cc: linux-bcachefs@vger.kernel.org, Brian Foster <bfoster@redhat.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
linux-kernel@vger.kernel.org, ltp@lists.linux.it
Subject: Re: [LTP] bcachefs fails to mount loop device on kernel
Date: Wed, 24 Jan 2024 22:07:38 +0100 [thread overview]
Message-ID: <20240124210738.GA352616@pevik> (raw)
In-Reply-To: <20240124205149.GA268968@fedora-laptop>
> On Wed, Jan 24, 2024 at 09:00:32PM +0100, Petr Vorel wrote:
> > Hi all,
> > bcachefs fails to mount loop device on kernel on both 6.7 and 6.8.0-rc1.
> > Is mounting loop even supported?
> > [...]
> > bcachefs mount /dev/loop0 /mnt
> > => Unknown command mount
> What version of the bcachefs CLI tool are you using? Is it distribution
> provided or did you build it yourself?
Official openSUSE Tumbleweed package:
$ rpm -qf $(which bcachefs)
bcachefs-tools-1.4.0-1.1.x86_64
BTW this was found with LTP, which has 2 APIs: C API, which uses mount(2)
which works well and shell API which uses mount (which uses bcachefs) and here
it fails.
Kind regards,
Petr
> The mount command has been implemented in Rust for a while (since
> 28f703cc256f "Rust now integrated into bcachefs binary") and if building
> without Rust support (BCACHEFS_NO_RUST defined), that command won't be
> included in the binary.
> In more recent versions of bcachefs-tools, building without Rust is not
> supported at all.
> I don't think this has anything to do with loop devices specifically.
> - Thomas Bertschinger
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-01-24 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 20:00 [LTP] bcachefs fails to mount loop device on kernel Petr Vorel
2024-01-24 20:51 ` Thomas Bertschinger
2024-01-24 21:07 ` Petr Vorel [this message]
2024-01-24 21:22 ` Kent Overstreet
2024-01-24 21:32 ` Petr Vorel
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=20240124210738.GA352616@pevik \
--to=pvorel@suse.cz \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=tahbertschinger@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