Hide Forgot
*** This bug has been marked as a duplicate of bug 708 ***
Posix locks do not work *correctly* on Solaris because of including types such as F_RDLCK, F_WRLCK, F_UNLCK from <fcntl.h> Linux: /usr/include/bits/fcntl.h:#define F_RDLCK 0 /* Read lock. */ /usr/include/bits/fcntl.h:#define F_WRLCK 1 /* Write lock. */ /usr/include/bits/fcntl.h:#define F_UNLCK 2 /* Remove lock.*/ Solaris: /usr/include/sys/fcntl.h:#define F_RDLCK 01 /* Read lock */ /usr/include/sys/fcntl.h:#define F_WRLCK 02 /* Write lock */ /usr/include/sys/fcntl.h:#define F_UNLCK 03 /* Remove lock(s) */ This was observed with process state dump when deadlocked using the ping-pong program on multiple mount points: <snip> xlator.feature.locks.lock-dump.domain.posixlk.posixlk[8](ACTIVE)=type=UNKNOWN, start=0, len=0, pid=0, lk-owner=11111567171309590679 xlator.feature.locks.lock-dump.domain.posixlk.posixlk[9](ACTIVE)=type=UNKNOWN, start=0, len=0, pid=0, lk-owner=11111567171309590679 xlator.feature.locks.lock-dump.domain.posixlk.posixlk[10](ACTIVE)=type=UNKNOWN, start=0, len=0, pid=0, lk-owner=11111567171309590679 xlator.feature.locks.lock-dump.domain.posixlk.posixlk[11](BLOCKED)=type=WRITE, start=0, len=1, pid=0, lk-owner=11111567171309590679 xlator.feature.locks.lock-dump.domain.posixlk.posixlk[12](ACTIVE)=type=READ, sta <snip>