Return-Path: Received: from biostat.ucsf.edu (upstrm185.psg-ucsf.org [38.99.193.74]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sat, 16 Jan 2010 01:30:26 +0100 (CET) From: Ross Boylan In-Reply-To: <20100115035805.GA31381@tansi.org> References: <20100113070157.GA13730@maude.comedia.it> <1263378036.3529.3.camel@Koma-Station.localdomain> <20100113131320.GA3993@tansi.org> <4B4DF253.5040201@whgl.uni-frankfurt.de> <20100113172946.GA6329@tansi.org> <4B4F600A.7090107@whgl.uni-frankfurt.de> <20100114214257.GB23608@tansi.org> <4B4F97BD.3020909@whgl.uni-frankfurt.de> <20100114224627.GA24444@tansi.org> <4B4FD035.2030705@whgl.uni-frankfurt.de> <20100115035805.GA31381@tansi.org> Content-Type: text/plain Date: Fri, 15 Jan 2010 16:30:11 -0800 Message-Id: <1263601811.26202.72.camel@corn.betterworld.us> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] renaming of device List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Arno Wagner Cc: dm-crypt@saout.de, ross@biostat.ucsf.edu On Fri, 2010-01-15 at 04:58 +0100, Arno Wagner wrote: > > Good idea, but no. Must be something in the udev configuration > after all. Not that I found anything. Or anything in the logs. > Hmm. Oh, well. It is not that important. But I really hate this > badly documented obscure "automagical" stuff. As soon as anything > breaks, it really sucks. > > On the side of where cryptsetup finds the device for a specific > major and minor number, it is indeed a simple recursive directory > traversal. Unfortunately it is in libdevmapper.c, i.e. in the > system lib of that name. That means it cannot easily be changed. I have a comment and a question. The comment is that I think udev on Debian has some private place that it stashes away mappings so that network cards (for sure) and disks (I think) have stable names. I think it's a Debian-specific feature, though other distros may do something similar. The question concerns the use of major:minor to identify devices. I thought the same physical device can have different major:minor on different boots.* Is that so, and if so, can it cause problems for dm-crypt, such as causing it to pick the wrong underlying volume? I'm pretty ignorant in this area so a) take what I say with a grain of salt and b) I'd appreciate any wisdom. Thanks. Ross Boylan *I think the Debian stuff stabilizes the relation between physical devices and names like /dev/sdd, but not necessarily physical devices and major:minor.