On Sat, Nov 21, 2020 at 01:51:42PM +0530, Sreyan Chakravarty wrote: > On Fri, Nov 20, 2020 at 4:45 PM Bryn M. Reeves <bmr@xxxxxxxxxx> wrote: > > > What type of snapshot are you using? LVM2 allows either "classic" CoW > > snaps, > > or the newer thin provisioned snapshots using the dm-thinp target. > > > > Classic snapshots are known to have very poor IO performance when multiple > > snapshots of the same volume exist simultaneously (especially for write- > > heavy workloads). > > > > Thin provisioned snapshots are not normally activated at boot time unless > > they are explicitly requested (via dracut's rd.lvm.lv options) since they > > have the skip activation flag set by default. > > > > I tried thin snapshots, but what use are they if I can't use my system all > together. I'm not following this statement. Can you explain what happened when you tried thin snapshots? > Once my root logical volume was marked read only I could not revert it back > to writable, after the snapshot was created. That's not a normal outcome of creating a snapshot - it sounds like you ran into some problem with the snaphot or the volume group, but without more details of the situation and what actually happened it's very hard to give you guidance to help avoid it in future. Regards, Bryn. _______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
