public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Levy <contact@ericlevy.name>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: option to mount read-only subvolume with read-write access
Date: Thu, 10 Nov 2022 05:12:52 -0500	[thread overview]
Message-ID: <G1N4LR.84UPK81F80SK3@ericlevy.name> (raw)

At times it is helpful to modify a subvolume to which has been assigned 
a read-only property, without changing the property. One reason for 
keeping the property is that the same subvolume may be reachable 
through another mount point. Another is to ensure that the property 
persists even if some operation fails to complete.

Would you consider adding a mount option to cause the system to ignore 
a read-only property for the subvolume accessed through the mount 
point, without affecting access to the same subvolume through other 
mount points?




             reply	other threads:[~2022-11-10 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 10:12 Eric Levy [this message]
2022-11-10 12:12 ` option to mount read-only subvolume with read-write access David Sterba
2022-11-10 13:50   ` Eric Levy
2022-11-10 16:46     ` Matthew Warren
2022-11-10 16:52       ` Eric Levy
2022-11-14 20:33     ` David Sterba
2022-11-14 21:11       ` Eric Levy

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=G1N4LR.84UPK81F80SK3@ericlevy.name \
    --to=contact@ericlevy.name \
    --cc=linux-btrfs@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