Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 07/19/2011 11:13 AM, listslut at outofoptions.net wrote:
> Quoting Digimer <linux at alteeve.com>:
>
>> On 07/19/2011 10:55 AM, listslut at outofoptions.net wrote:
>>> I can create a Volume Group and the data gets replicated from one
>>> machine to the other. This command fails though:
>>>
>>> [root at thing1 lvm]# /usr/sbin/lvcreate -n vmdata -l 69972 thing0
>>> Logging initialised at Tue Jul 19 10:53:21 2011
>>> Set umask to 0077
>>> Setting logging type to disk
>>> Finding volume group "thing0"
>>> Archiving volume group "thing0" metadata (seqno 15).
>>> Creating logical volume vmdata
>>> Creating volume group backup "/etc/lvm/backup/thing0" (seqno 16).
>>> Error locking on node thing1.eyemg.com: device-mapper: create ioctl
>>> failed: Device or resource busy
>>> Error locking on node thing2.eyemg.com: device-mapper: create ioctl
>>> failed: Device or resource busy
>>> Failed to activate new LV.
>>> Creating volume group backup "/etc/lvm/backup/thing0" (seqno 17).
>>> Wiping internal VG cache
>>>
>>> I don't know if this is a drbd issue or an lvm. I can't seem to find
>>> anything on it.
>>>
>>> Thanks
>>> Ken Lowther
>>
>> Obvius question first; Is the DRBD in Primary?
>
> It was primary/primary but this gave me an idea. I changed the 'other'
> node to secondary and it did change the error message some in that it
> gives a 'uuid not found' error instead on the second resource instead of
> the lock error.
>
> [root at thing1 lvm]# /usr/sbin/lvcreate -n vmdata -l 69972 thing0
> Logging initialised at Tue Jul 19 11:09:02 2011
> Set umask to 0077
> Setting logging type to disk
> Finding volume group "thing0"
> Archiving volume group "thing0" metadata (seqno 19).
> Creating logical volume vmdata
> Creating volume group backup "/etc/lvm/backup/thing0" (seqno 20).
> Error locking on node thing1.eyemg.com: device-mapper: create ioctl
> failed: Device or resource busy
> Error locking on node thing2.eyemg.com: Volume group for uuid not
> found: hqcys8c9fDoBtX4UGLV0lmAbTZ7FMW8516YBHLfh64TzKNxRBqDH1wYg7IQHMRul
> Failed to activate new LV.
> Creating volume group backup "/etc/lvm/backup/thing0" (seqno 21).
> Wiping internal VG cache
>
>
>>
>> Please share more details about your config so that folks can better
>> help you, rather than making wild stabs in the dark. :)
>>
> Using locking 3 in lvm with clvmd running.
> resource drbd0 {
> on thing1.eyemg.com {
> disk /dev/cciss/c0d1;
> device /dev/drbd0;
> meta-disk internal;
> address 192.168.244.1:7788;
> }
> on thing2.eyemg.com {
> disk /dev/cciss/c0d1;
> device /dev/drbd0;
> meta-disk internal;
> address 192.168.244.2:7788;
> }
> Ken
Can I assume then that the cluster itself is running and quorate? Also,
is anything else (trying to) use the backing devices? Does this error
occur on both nodes?
--
Digimer
E-Mail: digimer at alteeve.com
Freenode handle: digimer
Papers and Projects: http://alteeve.com
Node Assassin: http://nodeassassin.org
"At what point did we forget that the Space Shuttle was, essentially,
a program that strapped human beings to an explosion and tried to stab
through the sky with fire and math?"