When using locking, how can I determine what application caused corruption on nfs filesystem?

Solution In Progress - Updated -

Issue

  • When using NFSv4 with nfs locking with multiple clients, how can I determine what application caused corruption on my nfs shared filesystem?
  • How can I tell if 2 nfs clients are writing to the same file at the same time and what application/process is responsible?

Environment

  • Red Hat Enterprise Linux 5 or 6
  • NFS clients: two or more connected to same NFS server
  • NFS servers: one or more
  • NFSv4 locking
  • May involve Apache Active MQ Master and slave NFS clients or other multi-node configurations

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content