[Linux-cluster] GFS Problem

[Patricio A. Bruna]

Jos,
Im answering one by one

> -  Did you create the GFS filesystems with the correct locking
>    protocol (lock_dlm)?
Yes i did, like the documentations says: 
gfs_mkfs -p lock_dlm -t cluster_eseia:portales -j 4 /dev/CLUSTERLVM/portales

I used 4 journal, cause we are hoping to add 2 more nodes soon.

> -  Do you use clvmd?  Did you mark your VG's to be "clustered" and
>    do you have "locking_style = 3" in /etc/lvm/lvm.conf?

No i did not. By the way i only have locking_type in the file, i suppose is what you meant. Righ now is:
locking_type = 1

> > PD: Im attaching the cluster.conf. 
> 
> Where are the GFS filesystems in cluster.conf?
They arent, because they are supposed to start right away the server boot, and the services i have: IP and Perlbal, do not use the GFS filesystems.


In my logs files i saw this:

##################################
newton fenced[2394]: fencing node "davinci"
newton fenced[2394]: fence "davinci" failed
newton fenced[2394]: fencing node "davinci"
newton fenced[2394]: fence "davinci" failed
####################################

and after runnig the gfs_grow command in davinci:

####################################
Aug 11 04:06:10 newton kernel: attempt to access beyond end of device
Aug 11 04:06:10 newton kernel: dm-4: rw=0, want=270678704, limit=251658240
Aug 11 04:06:10 newton kernel: GFS: fsid=cluster_eseia:seiaprod-dig.0: fatal: I/O error
Aug 11 04:06:10 newton kernel: GFS: fsid=cluster_eseia:seiaprod-dig.0:   block = 33834837
Aug 11 04:06:10 newton kernel: GFS: fsid=cluster_eseia:seiaprod-dig.0:   function = gfs_dreread
Aug 11 04:06:10 newton kernel: GFS: fsid=cluster_eseia:seiaprod-dig.0:   file = /builddir/build/BUILD/gfs-kmod-0.1.16/_kmod_build_/src/gfs/dio.c, line = 576
Aug 11 04:06:10 newton kernel: GFS: fsid=cluster_eseia:seiaprod-dig.0:   time = 1186819570
Aug 11 04:06:10 newton kernel: GFS: fsid=cluster_eseia:seiaprod-dig.0: about to withdraw from the cluster
Aug 11 04:06:10 newton kernel: GFS: fsid=cluster_eseia:seiaprod-dig.0: telling LM to withdraw
Aug 11 04:06:11 newton kernel: dlm: drop message 11 from 1 for unknown lockspace 655362
Aug 11 04:06:11 newton kernel: GFS: fsid=cluster_eseia:seiaprod-dig.0: withdrawn
Aug 11 04:06:11 newton kernel:  [<f8d6d8ba>] gfs_lm_withdraw+0x76/0x82 [gfs]
Aug 11 04:06:11 newton kernel:  [<f8d81786>] gfs_io_error_bh_i+0x2c/0x31 [gfs]
Aug 11 04:06:11 newton kernel:  [<f8d5babd>] gfs_dreread+0x9f/0xbf [gfs]
Aug 11 04:06:11 newton kernel:  [<f8d5bafd>] gfs_dread+0x20/0x36 [gfs]
Aug 11 04:06:11 newton kernel:  [<f8d5d32b>] get_leaf+0x17/0x88 [gfs]
Aug 11 04:06:11 newton kernel:  [<f8d5de86>] gfs_dir_read+0x13f/0x68f [gfs]
Aug 11 04:06:11 newton kernel:  [<c05fadc5>] wait_for_completion+0x18/0x8d
Aug 11 04:06:11 newton kernel:  [<c041d186>] complete+0x2b/0x3d
Aug 11 04:06:11 newton kernel:  [<f8d750f0>] gfs_readdir+0xea/0x29e [gfs]
Aug 11 04:06:11 newton kernel:  [<f8d73de0>] filldir_reg_func+0x0/0x13b [gfs]
Aug 11 04:06:11 newton kernel:  [<c0479fc4>] filldir64+0x0/0xc5
Aug 11 04:06:11 newton kernel:  [<c045fdc9>] anon_vma_prepare+0x11/0xa5
Aug 11 04:06:11 newton kernel:  [<c0479fc4>] filldir64+0x0/0xc5
Aug 11 04:06:11 newton kernel:  [<c047a1a5>] vfs_readdir+0x63/0x8d
Aug 11 04:06:11 newton kernel:  [<c0479fc4>] filldir64+0x0/0xc5
Aug 11 04:06:11 newton kernel:  [<c047a232>] sys_getdents64+0x63/0xa5
Aug 11 04:06:11 newton kernel:  [<c0403eff>] syscall_call+0x7/0xb
Aug 11 04:06:11 newton kernel:  =======================
###############################################################################