From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phillip Susi Subject: Re: dm targets with spaces in the name Date: Mon, 8 Dec 2008 15:31:44 -0500 Message-ID: <493D8430.3010904@cfl.rr.com> References: <4936BBC6.7000800@cfl.rr.com> <1228405956.23557.74.camel@o> <49383A77.80903@cfl.rr.com> <20081205015938.GQ26097@agk.fab.redhat.com> <49395DB6.6050802@cfl.rr.com> <20081205170849.GC26097@agk.fab.redhat.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20081205170849.GC26097@agk.fab.redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: device-mapper development List-Id: dm-devel.ids Alasdair G Kergon wrote: > which is a bug as per what I stated above, if true. > > dmsetup knows nothing about the format of the table line - it's a simple > string - and should not be interfering with it: a backslash+space (after any > shell escaping) should get handled consistently, passed through to the target > and should work. Nevermind, I must have made a typeo before because now the kernel accepts targets with spaces in the name just fine, as long as they are properly backslash escaped. Heinz, you mentioned that dmraid should just not be using names with spaces in them. My first thought was to fix dmraid to backslash escape the spaces, but you seem to have another idea in mind?