Hi,
Masanari Iida wrote:
Hello Tao and Sunil,
] My case, the symptom (ocfs2 failed to mount a volume using
/etc/fstab) happend when I reboot the system.
Even if it failed to mount (by /etc/fstab), I can mount it later
after I login the system. So it could be some kind of timing issue.
Hello list,
There is a 14 node OCFS2 cluster.
When I reboot all 14 nodes at once, some node failed to
mount the ocfs2 filesystem while rebooting.
The mount is supposed to be done by /etc/fstab.
The symptom is happened on randam node.
I would like to know if there is such a rule that OCFS2 nodes
On Tue, Aug 5, 2008 at 5:43 PM, Tao Ma [EMAIL PROTECTED] wrote:
An error message I saw was
mount.ocfs2: Transport endpoint is not connected while mounting
/dev/EXTDISK/OCFS2
Interesting. Have you update ocfs2 in some nodes? Normally it happens when
there are some protocol collision among
Hi,
Masanari Iida wrote:
Hello list,
There is a 14 node OCFS2 cluster.
When I reboot all 14 nodes at once, some node failed to
mount the ocfs2 filesystem while rebooting.
The mount is supposed to be done by /etc/fstab.
The symptom is happened on randam node.
I would like to know if
Masanari Iida wrote:
On Tue, Aug 5, 2008 at 5:43 PM, Tao Ma [EMAIL PROTECTED] wrote:
An error message I saw was
mount.ocfs2: Transport endpoint is not connected while mounting
/dev/EXTDISK/OCFS2
Interesting. Have you update ocfs2 in some nodes? Normally it happens when
there
I believe 1.2.5-SLES-r2997 is the version of the fs and not the
tools. Meaning, an upgrade is required to the latest kernel
that is shipping 1.2.9.
As far as failure to mount goes, one reason could be that the
default timeout (10 secs) could be low. See if increasing to the
new default of 30 secs
