public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, Brian Foster <bfoster@redhat.com>,
	Thomas Bertschinger <tahbertschinger@gmail.com>,
	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:32:32 +0100	[thread overview]
Message-ID: <20240124213232.GA356523@pevik> (raw)
In-Reply-To: <5ykyohhnlc7nkbz7usc5sqmluyl7wgyhc6frqmbo5kk4vhuu3c@kgzze4c35gsv>

> On Wed, Jan 24, 2024 at 10:07:38PM +0100, Petr Vorel wrote:
> > > 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

> Sounds like Suse isn't building with our Rust code - but, that's about
> to become mandatory...

Indeed NO_RUST=1. Thank you both for a quick info!

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2024-01-24 21:32 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
2024-01-24 21:22     ` Kent Overstreet
2024-01-24 21:32       ` Petr Vorel [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240124213232.GA356523@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