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

[Linux-cluster] Problem running GFS on top of AoE



I'm trying to run GFS on top of AoE on my two-node cluster (node A and
B). I was using GNBD previously. 

I first exported a partition from A to B using vblade via eth1 (the
cluster is using eth0 I believe). That seems to work as expected. Then,
I did a gfs_mkfs on the etherd partition on B, and mounted the file
system on both A and B. All went as expected. But when I write stuff
onto the file system on either node, it takes a long time (a few
minutes) or never for the contents to be propagated to the other node.

I saw some abnormal messages in the log, but not quite sure what it
means. This is from node A, and similar messages are also in log from
node B. Any ideas? How should I trouble shoot this?

Feb 23 11:46:52 cfs2 kernel: GFS: fsid=gfs:aoe.1: Joined cluster. Now
mounting FS...
Feb 23 11:46:52 cfs2 kernel: GFS: fsid=gfs:aoe.1: jid=1: Trying to
acquire journal lock...
Feb 23 11:46:52 cfs2 kernel: GFS: fsid=gfs:aoe.1: jid=1: Trying to
acquire journal lock...
Feb 23 11:46:52 cfs2 kernel: GFS: fsid=gfs:aoe.1: jid=1: Looking at
journal...
Feb 23 11:46:52 cfs2 kernel: GFS: fsid=gfs:aoe.1: jid=1: Looking at
journal...
Feb 23 11:46:52 cfs2 kernel: GFS: fsid=gfs:aoe.1: jid=1: Done
Feb 23 11:46:52 cfs2 kernel: GFS: fsid=gfs:aoe.1: jid=1: Done
Feb 23 15:02:51 cfs2 kernel: device eth0 entered promiscuous mode
Feb 23 15:02:51 cfs2 kernel: device eth0 entered promiscuous mode
Feb 23 15:02:51 cfs2 kernel: device eth1 entered promiscuous mode
Feb 23 15:02:51 cfs2 kernel: device eth1 entered promiscuous mode
Feb 23 15:02:51 cfs2 kernel: device lo entered promiscuous mode
Feb 23 15:02:51 cfs2 kernel: device lo entered promiscuous mode

   


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