How to fix SCSI "reservation conflict" while using Veritas software?

Solution Verified - Updated -

Issue

  • In the systems log files, there are some messages with "SIGSEGV received", that indicates the application tried to access a memory area with no reference or undue, as follows:
    "SIGSEGV: A segmentation violation or segmentation fault typically means that something is trying to access memory that it shouldn't be 
    accessing."
  • In addition, there are a lot of scsi conflict errors into /var/log/messages
    Apr 12 07:01:30 hostname kernel: sd 3:0:0:28: reservation conflict
    Apr 12 07:01:30 hostname kernel: sd 3:0:0:28: reservation conflict
    Apr 12 07:01:30 hostname kernel: sd 3:0:0:29: reservation conflict
    Apr 12 07:01:30 hostname kernel: sd 3:0:0:29: reservation conflict
    Apr 12 07:01:30 hostname kernel: sd 3:0:0:30: reservation conflict
    Apr 12 07:01:30 hostname kernel: sd 3:0:0:30: reservation conflict

Environment

  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 6
  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 4
  • Veritas Volume Manager 3.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.