From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Date: Wed, 26 Apr 2017 09:26:36 +0200 From: Gionatan Danti In-Reply-To: <4b4d56ef-3127-212b-0e68-00b595faa241@redhat.com> References: <1438f48b-0a6d-4fb7-92dc-3688251e0a00@assyoma.it> <2f9c4346d4e9646ca058efdf535d435e@xenhideout.nl> <5df13342-8c31-4a0b-785e-1d12f0d2d9e8@redhat.com> <6dd12ab9-0390-5c07-f4b7-de0d8fbbeacf@redhat.com> <3831e817d7d788e93a69f20e5dda1159@xenhideout.nl> <0ab1c4e1-b15e-b22e-9455-5569eeaa0563@redhat.com> <51faeb921acf634609b61bff5fd269d4@xenhideout.nl> <4b4d56ef-3127-212b-0e68-00b595faa241@redhat.com> Message-ID: <0535f3d744145eceea9121b1e68b622d@assyoma.it> Subject: Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: LVM general discussion and development Cc: Xen , zkabelac@redhat.com Il 24-04-2017 23:59 Zdenek Kabelac ha scritto: > If you set '--errorwhenfull y' - it should instantly fail. It's my understanding that "--errorwhenfull y" will instantly fail writes which imply new allocation requests, but writes to already-allocated space will be completed. It is possible, without messing directly with device mapper (via dmsetup), to configure a strict "read-only" policy, where *all* writes (both to allocated or not allocated space) will fail? It is not possible to do via lvm tools, what/how device-mapper target should be used? Thanks. -- Danti Gionatan Supporto Tecnico Assyoma S.r.l. - www.assyoma.it email: g.danti@assyoma.it - info@assyoma.it GPG public key ID: FF5F32A8