archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <>
To: LVM general discussion and development <>,
	Pascal <>
Subject: Re: [linux-lvm] LVM and RO device/partition(s)
Date: Mon, 20 Mar 2023 14:57:49 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dne 19. 03. 23 v 11:27 Pascal napsal(a):
> hi,
> the bio_check_ro function of the blk-core.c source file of the Linux kernel 
> refers to LVM :
> <>
> how does LVM currently behave when faced with a device marked as readonly ?
> does it automatically switch itself in readonly mode?
> according to some tests carried out in a virtual machine, it seems that it 
> doesn't and that LVM modifies the disk/partition(s) even though they are all 
> readonly (chmod 444 && blockdev --setro).


There is no extra logic around RO devices in lvm2.  When lvm2 succeeds opening 
device in write mode, it'll use it for writing.

Also note - when you 'activate' a LV in read-write mode - someone opens such 
LV/device and you later on 'lvchange' such active LV to read-only mode - all 
writers will keep writing to such device.

It's not quite clear which kind of problem you are actually hitting - so maybe 
adding some more descriptive  environment +  logs  might give more info about 
your individual case.

Note: root admin typically can overwrite any 'mild' protections...



linux-lvm mailing list
read the LVM HOW-TO at

  reply	other threads:[~2023-03-20 14:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 10:27 [linux-lvm] LVM and RO device/partition(s) Pascal
2023-03-20 13:57 ` Zdenek Kabelac [this message]
2023-03-20 14:15   ` lacsaP Patatetom
2023-03-20 16:37     ` lacsaP Patatetom
2023-03-22 14:11       ` [linux-lvm] LVM and RO device/partition(s Zdenek Kabelac
2023-03-22 14:50         ` lacsaP Patatetom

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:

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

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).