[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Linux-cluster] Re: Still having GFS2 mount hang



Hi,

On Mon, 2009-06-08 at 18:37 -0400, William A. (Andy) Adamson wrote:
> Hello
> 
> I'm still not able to mount GFS2 on both of my 2 node cluster nodes at
> once. Please! Any help is welcome...
> 
> Setup: 2 Fedora 10 VM sharing disk over AOE from third vm machine.
> 2.6.30-rc7 kernel with latest Fedora 10 rpm updates. The cluster.conf
> is attached.
> 
> I gdb'ed mount.gfs2 on the 2nd node - it hangs trying to read in gfsc_fs_result.
> 
> -->Andy
> 
> gfs2_controld -D output on first node: mount /gfs2.
> 
> 1244499915 client connection 6 fd 17
> 1244499915 join: /gfs2 gfs2 lock_dlm androsGFS2:ClusterFS rw,noauto
> /dev/etherd/e3.2p1
> 1244499915 ClusterFS join: cluster name matches: androsGFS2
> 1244499915 ClusterFS process_dlmcontrol register nodeid 0 result 0
> 1244499915 ClusterFS add_change cg 1 joined nodeid 2
> 1244499915 ClusterFS add_change cg 1 we joined
> 1244499915 ClusterFS add_change cg 1 counts member 1 joined 1 remove 0 failed 0
> 1244499915 ClusterFS wait_conditions skip for zero started_count
> 1244499915 ClusterFS send_start cg 1 id_count 1 om 0 nm 1 oj 0 nj 0
> 1244499915 ClusterFS receive_start 2:1 len 92
> 1244499915 ClusterFS match_change 2:1 matches cg 1
> 1244499915 ClusterFS wait_messages cg 1 got all 1
> 1244499915 ClusterFS pick_first_recovery_master low 2 old 0
> 1244499915 ClusterFS sync_state all_nodes_new first_recovery_needed master 2
> 1244499915 ClusterFS create_old_nodes all new
> 1244499915 ClusterFS create_new_nodes 2 ro 0 spect 0
> 1244499915 ClusterFS create_failed_journals all new
> 1244499915 ClusterFS create_new_journals 2 gets jid 0
> 1244499915 ClusterFS apply_recovery first start_kernel
> 1244499915 ClusterFS start_kernel cg 1 member_count 1
> 1244499915 ClusterFS set
> /sys/fs/gfs2/androsGFS2:ClusterFS/lock_module/block to 0
> 1244499915 ClusterFS set open
> /sys/fs/gfs2/androsGFS2:ClusterFS/lock_module/block error -1 2
This is returning -ENOENT. Do you have sysfs mounted somewhere strange?

> 1244499915 ClusterFS client_reply_join_full ci 6 result 0
> hostdata=jid=0:id=1562653156:first=1
> 1244499915 client_reply_join ClusterFS ci 6 result 0
> 1244499915 uevent: add@/fs/gfs2/androsGFS2:ClusterFS
> 1244499915 kernel: add@ androsGFS2:ClusterFS
> 1244499915 uevent: change@/fs/gfs2/androsGFS2:ClusterFS
> 1244499915 kernel: change@ androsGFS2:ClusterFS
> 1244499915 uevent: change@/fs/gfs2/androsGFS2:ClusterFS
> 1244499915 kernel: change@ androsGFS2:ClusterFS
> 1244499915 uevent: change@/fs/gfs2/androsGFS2:ClusterFS
> 1244499915 kernel: change@ androsGFS2:ClusterFS
> 1244499915 mount_done: ClusterFS result 0
> 1244499915 connection 6 read error -1
I'm not sure if this is "normal" or not, but it may well point towards
what is going wrong here,

Steve.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]