public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alec Moskvin <list.bcachefs@e.netreq.com>
To: linux-bcachefs@vger.kernel.org
Subject: fsck: bch2_parse_mount_opts() Bad mount option read_only
Date: Sun, 14 Jan 2024 18:55:03 -0500	[thread overview]
Message-ID: <20240114235503.GA269705@emmetten> (raw)

On Linux 6.7.0 with the latest bcachefs-tools 1.4.0, I get an error when 
trying to run fsck:

    bcachefs fsck -v /dev/sda3
    bch2_parse_mount_opts() Bad mount option read_only

If I try a newer git revision of bcachefs-tools, it works but does an 
upgrade of the fs version:

    bcachefs fsck /dev/sda3
    mounting version 1.3: rebalance_work opts=ro,compression=zstd:15,degraded,verbose,fsck,fix_errors=ask,read_only
    recovering from clean shutdown, journal seq 116268
    Doing compatible version upgrade from 1.3: rebalance_work to 1.4: member_seq 

and then when I mount it, it downgrades:

    [Jan14 11:06] bcachefs (sda3): mounting version 1.4: (unknown version) opts=compression=zstd:15
    [  +0.000016] bcachefs (sda3): recovering from clean shutdown, journal seq 116272
    [  +0.000003] bcachefs (sda3): Version downgrade required:
    
    [  +0.200171] bcachefs (sda3): alloc_read... done

Is there a correspondence between the kernel and bcachefs-tools 
versions? I.e., should bcachefs-tools 1.3.6 be used until a kernel with 
bcachefs 1.4 is released?

Thanks,
Alec

             reply	other threads:[~2024-01-15  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14 23:55 Alec Moskvin [this message]
2024-01-16 16:31 ` fsck: bch2_parse_mount_opts() Bad mount option read_only Kent Overstreet

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=20240114235503.GA269705@emmetten \
    --to=list.bcachefs@e.netreq.com \
    --cc=linux-bcachefs@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