From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n36MkIo2022393 for ; Mon, 6 Apr 2009 18:46:18 -0400 Received: from n8.bullet.re3.yahoo.com (n8.bullet.re3.yahoo.com [68.142.237.93]) by mx1.redhat.com (8.13.8/8.13.8) with SMTP id n36MjtR1018316 for ; Mon, 6 Apr 2009 18:45:55 -0400 From: "Theophanis Kontogiannis" Date: Tue, 7 Apr 2009 01:45:48 +0300 Message-ID: <004b01c9b709$6f1b7970$4d526c50$@gr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004C_01C9B722.9468B170" Content-Language: el Subject: [linux-lvm] Why the problem with LVcreate with a specific name? 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: To: linux-lvm@redhat.com This is a multipart message in MIME format. ------=_NextPart_000_004C_01C9B722.9468B170 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: 7bit Hello all, I have CentOS 5.3 with: lvm2-2.02.40-6.el5 system-config-lvm-1.1.5-1.0.el5 lvm2-cluster-2.02.40-7.el5 I try to create a new full disk clustered LV When I do [root@tweety-1 /]# lvcreate -v -L 931.48G -n data2 vg1 Setting logging type to disk Finding volume group "vg1" Rounding up size to full physical extent 931.48 GB Archiving volume group "vg1" metadata (seqno 21). Creating logical volume data2 Creating volume group backup "/etc/lvm/backup/vg1" (seqno 22). Clearing start of logical volume "data2" Creating volume group backup "/etc/lvm/backup/vg1" (seqno 22). Logical volume "data2" created [root@tweety-1 /]# lvdisplay --- Logical volume --- LV Name /dev/vg1/data2 VG Name vg1 LV UUID xA0oky-7VaD-P8a3-8aAC-2jGy-R9Ij-1L3bvR LV Write Access read/write LV Status available # open 0 LV Size 931.48 GB Current LE 238459 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:2 It gets created succefully. When I run the same command but with data1 instead of data2, I get the following error: [root@tweety-1 /]# lvcreate -v -L 931.48G -n data1 vg1 Setting logging type to disk Finding volume group "vg1" Rounding up size to full physical extent 931.48 GB Archiving volume group "vg1" metadata (seqno 23). Creating logical volume data1 Creating volume group backup "/etc/lvm/backup/vg1" (seqno 24). Error locking on node tweety1: device-mapper: create ioctl failed: Device or resource busy Aborting. Failed to activate new LV to wipe the start of it. Creating volume group backup "/etc/lvm/backup/vg1" (seqno 25). Could you help me find out what is blocking data1 as a valid name? I am lost and I do not know where to start from. Thank you all for your time. Theophanis Kontogiannis. ------=_NextPart_000_004C_01C9B722.9468B170 Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable

Hello all,

 

I have CentOS 5.3 = with:

 

lvm2-2.02.40-6.el5

system-config-lvm-1.1.5-1.0.el5

lvm2-cluster-2.02.40-7.el5

 

I try to create a new full disk = clustered LV

 

When I do [root@tweety-1 /]# = lvcreate -v -L 931.48G -n data2 vg1

=A0=A0=A0 Setting logging type = to disk

=A0=A0=A0 Finding volume group = "vg1"

=A0 Rounding up size to full = physical extent 931.48 GB

=A0=A0=A0 Archiving volume group = "vg1" metadata (seqno 21).

=A0=A0=A0 Creating logical = volume data2

=A0=A0=A0 Creating volume group = backup "/etc/lvm/backup/vg1" (seqno 22).

=A0=A0=A0 Clearing start of = logical volume "data2"

=A0=A0=A0 Creating volume group = backup "/etc/lvm/backup/vg1" (seqno 22).

=A0 Logical volume = "data2" created

[root@tweety-1 /]# = lvdisplay

=A0 --- Logical volume = ---

=A0 LV = Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = /dev/vg1/data2

=A0 VG = Name=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = vg1

=A0 LV = UUID=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 xA0oky-7VaD-P8a3-8aAC-2jGy-R9Ij-1L3bvR

=A0 LV Write = Access=A0=A0=A0=A0=A0=A0=A0 read/write

=A0 LV = Status=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = available

=A0 # = open=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = 0

=A0 LV = Size=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 931.48 = GB

=A0 Current = LE=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 238459

=A0 = Segments=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = 1

=A0 = Allocation=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 = inherit

=A0 Read ahead = sectors=A0=A0=A0=A0 auto

=A0=A0- currently set = to=A0=A0=A0=A0 256

=A0 Block = device=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 253:2

 

It gets created = succefully.

 

When I run the same command but = with data1 instead of data2, I get the following error:

 

[root@tweety-1 /]# lvcreate -v = -L 931.48G -n data1 vg1

=A0=A0=A0 Setting logging type = to disk

=A0=A0=A0 Finding volume group = "vg1"

=A0 Rounding up size to full = physical extent 931.48 GB

=A0=A0=A0 Archiving volume group = "vg1" metadata (seqno 23).

=A0=A0=A0 Creating logical = volume data1

=A0=A0=A0 Creating volume group = backup "/etc/lvm/backup/vg1" (seqno 24).

=A0 Error locking on node = tweety1: device-mapper: create ioctl failed: Device or resource = busy

=A0 Aborting. Failed to activate = new LV to wipe the start of it.

=A0=A0=A0 Creating volume group = backup "/etc/lvm/backup/vg1" (seqno 25).

 

Could you help me find out what = is blocking data1 as a valid name?

 

I am lost and I do not know = where to start from.

 

Thank you all for your = time.

 

Theophanis = Kontogiannis.

 

------=_NextPart_000_004C_01C9B722.9468B170--