RO device/partition "tampered" by LVM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hello developers,

until recently, I used to modify the `bio_check_ro` function of the
`block/blk-core.c` file to prevent LVM from altering read-only
partitions.

is it possible to get this behavior back after the many changes
applied to the `block/blk-core.c` file and especially to the
`bio_check_ro` function ?
if yes, can you tell me how to do it ?
otherwise, would retrograde only the `block/blk-core.c` file in a
previous version work ?

here is a GitHub page that details what I said :
https://github.com/patatetom/lvm-on-readonly-block-device .

on this subject, do you know of any other technologies such as LVM
that would alter a disk or partition marked as read-only, which would
ignore the administrator's wish ?

regards, lacsaP.



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux