Quantum Forum V

Quantum Forum for DXi V5000

The log /var/log/messeges is below:

fsm: StorNext FSS '[0]': PANIC: /usr/cvfs/bin/fsm ASSERT failed "ha_smith_interval >= MIN_HA_INTERVAL && ha_smith_interval <= MAX_HA_INTERVAL" file /home/mlund/nightly/VM-0-RedHat50AS-26x86-64-SP0/sn/snfs/fsm/fsm.c, line 1660
Nov 5 13:42:39 DXi000C29FB1EA1 fsm: PANIC: /usr/cvfs/bin/fsm ASSERT failed "ha_smith_interval >= MIN_HA_INTERVAL && ha_smith_interval <= MAX_HA_INTERVAL" file /home/mlund/nightly/VM-0-RedHat50AS-26x86-64-SP0/sn/snfs/fsm/fsm.c, line 1660
Nov 5 13:42:39 DXi000C29FB1EA1 fsm: StorNext FSS '[0]': FsmPmConnect failed: The File System Services on 127.0.0.1 may be stopped.
Nov 5 13:42:39 DXi000C29FB1EA1 fsm: StorNext FSS '[0]': PANIC: aborting threads now.

Views: 36

Reply to This

Replies to This Discussion

the photo from webservice

Attachments:

the photo from console ehrn you will see status of system

Attachments:

[root@DXi000C29FB1EA1 ~]# cvfsck
Checked Build disabled - default.
StorNext File Systems on host DXi000C29FB1EA1:

1) vol0

Choose a file system by number (1-1) or zero (0) to exit -> 1

*Fatal*: Failed to connect to fsmpm.

*Fatal*: Failed to register with fsmpm

*Critical*: File System Check finished - with errors.

[root@DXi000C29FB1EA1 ~]# cat /etc/fstab
LABEL=/ / ext3 defaults,noatime,nodiratime 1 1
#LABEL=/altboot /altboot ext3 defaults,noatime,nodiratime 1 2
LABEL=/var /var ext3 defaults,noatime,nodiratime 1 2
LABEL=/scratch /scratch ext3 defaults,noatime,nodiratime 1 2
#LABEL=/altroot /altroot ext3 defaults,noatime,nodiratime 1 2
LABEL=/boot /boot ext3 defaults,noatime,nodiratime 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-sda6 swap swap defaults 0 0
vol0 /snfs cvfs noatime,cachebufsize=256k,buffercache_iods=64,buffercachecap=128,nfsopen=yes,timeout=600 0 0

-----ATNTION---

I haven't driver cvfs in /dev/directory!

Hello  Pawel,

It looks like something is preventing the store next file system from mounting. This can happen when power is suddenly  lost to the DXI v1000.

In cases like these, support would need to access the DXi v1000 and attempt to gather logs so analysis can be done to determine what exactly happened. Typically these case are then escalated to our back line engineering teams who provide the resolution to bring the DXi v1000 back online and recover any data that may be corrupted.

Due to the nature of this case you would need a support contract so the technical support team can assist you to bring the DXi v1000 back online.

Hi Jerry, yesterday I checked the new version of DXI v1000 and I'm verry happy because the new version works great.

So, we have the answer and solution.

Than you for answer.

RSS

Tips + Tricks

© 2024   Created by Quantum Forum V.   Powered by

Badges  |  Report an Issue  |  Terms of Service