From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alan D. Brunelle" Subject: Problem w/ Date: Thu, 28 Aug 2008 17:19:32 -0400 Message-ID: <48B71664.4030701@hp.com> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: 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 I'm attempting to boot a recent 2.6.27-rc4 based kernel, but have run into a strange thing: Setting up Logical Volume Management: Failed to format device number for as dm target (259,987136) 1 logical volume(s) in volume group "oralogvg1" now active Failed to format device number for as dm target (259,1003520) 1 logical volume(s) in volume group "oralogvg2" now active Failed to format device number for as dm target (259,905216) Failed to format device number for as dm target (259,905216) 2 logical volume(s) in volume group "oradbvg" now active This is (at least) due to an issue in the DM library: it only has room for 10 total character in some names, and with: 259:1003520 259:905216 We exceed the size (need room for the '\0'). I don't know why the minors all of a sudden became so huge (is this normal?) but I /can/ access the devices themselves. Version information below: root@tin(root):pvs --version LVM version: 2.02.26-RHEL5 (2007-08-09) Library version: 1.02.20 (2007-06-15) Driver version: 4.14.0 Is there some up-stream patch in the DM Library that has larger sizes available for use? Thanks, Alan