<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: LVM Locks in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446485#M561497</link>
    <description>Shalom KPS,&lt;BR /&gt;&lt;BR /&gt;You would see these type of messages to standard output when you try and run the vgimport command.&lt;BR /&gt;&lt;BR /&gt;I think you would also see this in dmesg and syslog.log. One might try to do this on a test system to be certain.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Wed, 24 Jun 2009 18:30:49 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2009-06-24T18:30:49Z</dc:date>
    <item>
      <title>LVM Locks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446484#M561496</link>
      <description>A quick LVM question with regard to lvm locks.  If we were attempting to run a vgimport and there was already an LVM operation in progress, would we see a LVM lock error or message in the syslog.log related to this?   Do these type of events normally write to the syslog.log?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;KPS</description>
      <pubDate>Wed, 24 Jun 2009 17:49:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446484#M561496</guid>
      <dc:creator>KPS</dc:creator>
      <dc:date>2009-06-24T17:49:46Z</dc:date>
    </item>
    <item>
      <title>Re: LVM Locks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446485#M561497</link>
      <description>Shalom KPS,&lt;BR /&gt;&lt;BR /&gt;You would see these type of messages to standard output when you try and run the vgimport command.&lt;BR /&gt;&lt;BR /&gt;I think you would also see this in dmesg and syslog.log. One might try to do this on a test system to be certain.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 24 Jun 2009 18:30:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446485#M561497</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-06-24T18:30:49Z</dc:date>
    </item>
    <item>
      <title>Re: LVM Locks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446486#M561498</link>
      <description>Hi KPS:&lt;BR /&gt;&lt;BR /&gt;The '/etc/lvmconf/lvm_lock' file prevents multiple LVM processes from accessing the '/etc/lvmtab' at the same time.&lt;BR /&gt;&lt;BR /&gt;I'm not sure if this is "can't lock" errors are recorded in the 'syslog.log'.&lt;BR /&gt;&lt;BR /&gt;What are you trying to do?  What problem are you experiencing?  What error message(s) are you seeing?  A description of your environment would be helpful too.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 24 Jun 2009 18:34:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446486#M561498</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-06-24T18:34:14Z</dc:date>
    </item>
    <item>
      <title>Re: LVM Locks</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446487#M561499</link>
      <description>We have a server that runs multiple backups via BCV.  The times of when the various VG's and filesystems get activated and mounted are staggered to attempt to avoid LVM locks.   Yesterday we added in an additional backup and the vgimport did not work and we don't even see any sign of the vgimport attempting to run of the volume group against the mapfile that we intend to use in the syslog.log.  We cannot duplicate this issue off peak hours and our scripts work just great when run manually and not from a scheduled manner. &lt;BR /&gt;&lt;BR /&gt;The above is why I was asking if LVM Lock issues would be recorded to the syslog.log.  We may need to enhance the logging to see where the break point is.&lt;BR /&gt;&lt;BR /&gt;Thanks to the both of you for your responses.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;/KPS</description>
      <pubDate>Wed, 24 Jun 2009 18:42:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvm-locks/m-p/4446487#M561499</guid>
      <dc:creator>KPS</dc:creator>
      <dc:date>2009-06-24T18:42:06Z</dc:date>
    </item>
  </channel>
</rss>

