[Linux-cluster] Re: Dodgy Mounting
Steve Nelson
sanelson at gmail.com
Sat Sep 17 20:09:33 UTC 2005
On 9/17/05, Steve Nelson <sanelson at gmail.com> wrote:
> Hello,
>
> GFS6.0 // RHEL 3.0
>
> Perfectly normal set-up - assembled pools and cluster archives, got
> lock_gulmd working, and made mountpoints and entries in /etc/fstab
>
> Mount /archive
>
> # mount /archive
> mount: wrong fs type, bad option, bad superblock on /dev/pool/gfs0,
> or too many mounted file systems
Ok - so this looks like a generic error - looking further, dmesg shows:
GFS: can't mount proto = lock_gulm, table = digex:gfs3, hostdata =
lock_gulm: ERROR Core returned error 1003:Bad Cluster ID.
lock_gulm: ERROR cm_login failed. 1003
lock_gulm: ERROR Got a 1003 trying to start the threads.
lock_gulm: fsid=digex:gfs0: Exiting gulm_mount with errors 1003
etc for various tables.
> Steve
S.
More information about the Linux-cluster
mailing list