Skip to Main Content

Infrastructure Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

HA error opening /poolfsmnt/.../server_pool

joguerraJan 28 2015 — edited Feb 9 2015

Hi

I've an OracleVM 3.3.1 cluster environment with two nodes running (16cores + 32GB RAM + 12 VMs in total and **everything** is running ok) and after a while, I realized that the Repository was flagged with warning sign. Looking at the dom0 log file ovs-agent.log, I checked out that is complaining with the following message:

[2015-01-28 09:48:04 3339] ERROR (ha:110) Error in HA process: Open file: /poolfsmnt/0004fb00000500006c8e7a8c3decca89/db/server_pool failed: [Errno 30] Read-only file system: '/poolfsmnt/0004fb00000500006c8e7a8c3decca89/db/server_pool'

Traceback (most recent call last):

  File "/usr/lib64/python2.6/site-packages/agent/daemon/ha.py", line 104, in serve_forever

    if is_clustered() and is_master():

  File "/usr/lib64/python2.6/site-packages/agent/lib/settings.py", line 144, in is_master

    get_cluster_db_home())

  File "/usr/lib64/python2.6/site-packages/agent/lib/db.py", line 90, in read_item

    db = AgentDB(db_name, db_home)

  File "/usr/lib64/python2.6/site-packages/agent/lib/db.py", line 45, in __init__

    self.lock.acquire(wait=10, delay=0.1)

  File "/usr/lib64/python2.6/site-packages/agent/lib/filelock.py", line 43, in acquire

    raise LockError("Open file: %s failed: %s" % (self.filename, e))

LockError: Open file: /poolfsmnt/0004fb00000500006c8e7a8c3decca89/db/server_pool failed: [Errno 30] Read-only file system: '/poolfsmnt/0004fb00000500006c8e7a8c3decca89/db/server_pool'

The repository is mounted over an EMC2 FC storage and I am using OCFS2.  As far I can determine, the multipath is ok and the storage doesn't squawk any error/warning message. All the VMs are running okay, the dmesg at the dom0 is throwing this error though:

(kworker/u:1,10407,5):ocfs2_check_dir_entry:340 ERROR: bad entry in directory #37: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

(kworker/u:1,10407,5):ocfs2_check_dir_entry:340 ERROR: bad entry in directory #38: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

(kworker/u:1,10407,5):ocfs2_check_dir_entry:340 ERROR: bad entry in directory #39: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

(kworker/u:1,10407,5):ocfs2_check_dir_entry:340 ERROR: bad entry in directory #40: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

(kworker/u:1,10407,5):ocfs2_check_dir_entry:340 ERROR: bad entry in directory #41: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

(kworker/u:1,10407,5):ocfs2_check_dir_entry:340 ERROR: bad entry in directory #42: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

(kworker/u:1,10407,5):ocfs2_check_dir_entry:340 ERROR: bad entry in directory #43: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

It seems to me, the error is related to OCSF2 issues, but does anybody have a clue about this errors? I inclined to say there is some sort of corruption on the filesystem anyway.

Cheers

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 9 2015
Added on Jan 28 2015
9 comments
2,069 views