Re: Unable to deactivate lv, pehaps due to semaphore problem...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dne 27.11.2014 v 16:01 Gianluca Cecchi napsal(a):
On Thu, Nov 27, 2014 at 3:33 PM, Zdenek Kabelac <zkabelac@xxxxxxxxxx
<mailto:zkabelac@xxxxxxxxxx>> wrote:

    Dne 27.11.2014 v 15:26 Gianluca Cecchi napsal(a):

        Hello,
        I'm unable to deactivate an lvm.

        My system is RHEL 6.5 with lvm2-2.02.100-8.el6.x86_64 and kernel
        2.6.32-431.29.2.el6.x86_64

        I get error code 5 with message
            Logical volume VG_AAA_TEMP/LV_AAA_TEMP in use.

        You can find output of
        lvchange -d -d -d -d -d -d -an VG_AAA_TEMP/LV_AAA_TEMP
        here:
        https://drive.google.com/file/__d/__0BwoPbcrMv8mvTjlBMkRUbG9nczA/__view?usp=sharing
        <https://drive.google.com/file/d/0BwoPbcrMv8mvTjlBMkRUbG9nczA/view?usp=sharing>


    Not really accessible.


strange, do you mean the google docs link?
I tried with a browser without access to any gmail account and I'm able to
download it....


Ahh - I'd too strict  adblock filter - however passed info is not that useful.
Prefered output is   'lvchange -vvvv -an'



    But anyway - if you have problem with  'semaphore' resouces - you could
    'recycle' old ones -

    'dmsetup  udevcomplete_all'


This is actually a production server with many other LVs... Is there any
drawback in the command above?

You could 'complete' all cookies older then i.e. 1 minute.
Nothing should be holding cookie for that long time.


Nov 26 17:35:34 orapr2 rgmanager[5908]: [lvm] lv_activate_resilient stop
failed on VG_AAA_TEMP/LV_AAA_TEMP
Nov 26 17:35:34 orapr2 rgmanager[5928]: [lvm] Unable to deactivate
VG_AAA_TEMP/LV_AAA_TEMP

Well - here we need to know the reason why it has failed -

Is there some user of  VG_AAA_TEMP/LV_AAA_TEMP ?

Mounted, opened, used as a device for something else ?


        [root@orapr2 ~]# lvs VG_AAA_TEMP/LV_AAA_TEMP
            LV          VG          Attr       LSize    Pool Origin Data%
        Move Log
        Cpy%Sync Convert
            LV_AAA_TEMP VG_AAA_TEMP -wi-ao---- 1020.00m

        How can I see the responsible for the reference that apparently keeps
        it open?

        Open count:        1
        so I can check and eventually fix??

lsof  - look for user of 253,49

Zdenek

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel




[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux