From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Mon, 16 Nov 2009 14:48:24 +0100 (CET) Message-ID: <4B01581F.2000109@redhat.com> Date: Mon, 16 Nov 2009 14:48:15 +0100 From: Milan Broz MIME-Version: 1.0 References: <8753c5d10911160527r1c66f204tc6bf7d7b3841ee15@mail.gmail.com> In-Reply-To: <8753c5d10911160527r1c66f204tc6bf7d7b3841ee15@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] Option --non-exclusive and scubed support for luks device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: MatriX Cc: dm-crypt@saout.de On 11/16/2009 02:27 PM, MatriX wrote: > i don't found info about obsolete option "--non-exclusive". > In the help of cryptsetup is written "Allows non-exclusive access for > luksOpen, WARNING see manpage." but in manpage i don't found anything. > Can scubed work with luks device? > I think this "obsolete" option is needed for that... I'll add something to man page, but --non-exclusive option is ignored in new code and will be no longer supported, because it can lead to data corruption. I am not sure why scubed need that - can you point me to recent source code? The only use for it now is allow to open copy of LUKS volume with the same UUID, (hw snapshot or so) in cryptsetup 1.0.7. In 1.1.0-rc it is fixed differently. (see issue 34 on project pages for more details) Milan -- mbroz@redhat.com