The last ebuilds for packages specified in the summary in portage are 1.04.00 and now versions 2.00.00 for them are availables. This is a request to bump the gentoo's portage versions to the latest published by mainstream. Reproducible: Always
gfs2 is simply not ready for production.
Christian: GFS2 is included in the default kernel, why not provide userspace-tools?
GFS2 in kernel mainline since 2.6.19 Current version is 2.6.22
Any news on this? It is now 3 months later. GFS2 is still in the stable Linux kernel. The older version of GFS no longer compiles against the latest kernel. We're blocked in front and behind. Are we close to having GFS2 in portage yet?
(In reply to comment #1) > gfs2 is simply not ready for production. Is there an expanded answer to why its felt that gfs2 is not ready for production? It would be nice to know what work needs doing i.e. gfs2 isn't ready because of x,y and z. That way people can offer help as and where they can.
I too would be interested in any movement on this. If, like me, you want this now then the ebuilds on bug #203916 and bug #160847 worked fine for me with a recent kernel. dev-perl/Net-Telnet might also be required. There is also bug #201132 and bug #195730 but these seem less useful. I'm not condoning the ebuilds -- they obviously need some work -- I am just being pragmatic rather than politic. You can then probably add the following to /etc/portage/profile/package.provided sys-cluster/magma-2.01.00 sys-cluster/cman-headers-2.01.00 sys-cluster/iddev-2.01.00 sys-cluster/gfs-headers-2.01.00 sys-cluster/dlm-headers-2.01.00 sys-cluster/ccs-2.01.00 sys-cluster/dlm-2.01.00 sys-cluster/magma-plugins-2.01.00 sys-cluster/cman-2.01.00 sys-cluster/fence-2.01.00 sys-fs/gfs-2.01.00 Again, not condoning this, just stating its effectiveness.
*** Bug 205754 has been marked as a duplicate of this bug. ***
Created attachment 140919 [details] for redhat cluster suite 2.01.00
(In reply to comment #8) > Created an attachment (id=140919) [edit] > for redhat cluster suite 2.01.00 > as stated on the homepage, cluster-2.xx is "Cluster Components - New": http://sources.redhat.com/cluster/ there are so many differences between cluster-2.xx with cluster-1.xx: so I will plan to add these ebuilds: sys-cluster/ccs-2.01.00 sys-cluster/dlm-2.01.00 sys-cluster/cman-2.01.00 sys-cluster/cman-lib-2.01.00 sys-cluster/fence-2.01.00 sys-fs/gfs2-2.01.00 these packages not needed in the new components arch: sys-cluster/magma-2.01.00 (for locking module merged into the kernel,) sys-cluster/cman-headers-2.01.00 (cman has revamped with a userspace implementaion, so kernel headers not needed) sys-cluster/iddev-2.01.00 sys-cluster/gfs-headers-2.01.00 sys-cluster/dlm-headers-2.01.00 sys-cluster/magma-plugins-2.01.00 the new cman-2.01.00 depends on a library openais-0.80.3 (on #160847), please test it.
Created attachment 141019 [details] Updated ebuilds for the cluster suite packages. Includes updated ebuilds and scripts for all the packages in 2.01.00 of the cluster suite: openais (with a different SBINDIR) cman-lib ccs cman dlm fence rgmanager gnbd gnbd-kernel gfs-kernel gfs gfs2 If need be I can upload them individually, but that seemed like such a pain - there are many files. I've tested everything except gnbd and rgmanager. I've also tested it with lvm2 with USE="cman clvm". The utilities should still work with the original GFS, so upgrading isn't a problem, though I haven't tested that yet either.
Is there any howto to run this ?
(In reply to comment #11) > Is there any howto to run this ? > I'm assuming you know how to do a portage overlay and unmask packages. If not, read up here: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=5#doc_chap2 Basically "emerge gfs", or "emerge gfs2" (which is still under development). If you turn on USE=doc, then there's a file that gets created in /usr/share/doc/gfs*/usage.txt.bz2. Have a look at that for a basic install how to. Also have a look here, in particular at the faq. The usage.txt is also online there. http://sources.redhat.com/cluster/ I'll probably spend some time writing up a wiki/forum entry later, but there's not much more to it than what the usage.txt has to say. A quick summary: emerge gfs vim /etc/cluster/cluster.conf scp cluster.conf hosts{1,...,n} /etc/init.d/fenced start mkfs.gfs /dev/somedev mount -t gfs /dev/somedev /mnt/pnt Also, have a look here: http://forums.gentoo.org/viewtopic-p-4746725.html So as not to pollute this bug (which I've been scolded for before), I kept a slightly more up to date set of ebuilds in the link in that forum. The init scripts are just a little bit better, that's all.
i mean some info on configuring gfs2 =) i'll tryed to config it to use with clvm
(In reply to comment #13) > i mean some info on configuring gfs2 =) > i'll tryed to config it to use with clvm > sed 's/gfs/gfs2/g' previous_example As in, it's the exact same process, just replace gfs, with gfs2. When you do that try something like this and let me know how it goes: cssh node1 node2 cd /mnt/gfs2 for i in `seq 1 1000`; do echo $HOSTNAME >> $i.txt; done ls -l rm -v *.txt The last line always deadlocked with me. Both nodes thought the other held the lock on one of the files. Hence, I'm inclined to agree with Comment #1. Even the RedHat guys say so.
(In reply to comment #5) > (In reply to comment #1) > > gfs2 is simply not ready for production. > > Is there an expanded answer to why its felt that gfs2 is not ready for > production? > Because RedHat says so is... I think, a good reason. From the FAQ http://sources.redhat.com/cluster/faq.html#gfs2_convert "WARNING: At this time, gfs2 is still being worked on, so you should not use it for a production cluster." So hey, you have a safe (gfs1) version, and a less safe (gfs2) version. For a production cluster with data that just can't be messed with, using gfs1 seems like a good choice.
(In reply to comment #15) Definitely. My take on these ebuilds right now is that since gfs1 with cluster-1.x doesn't build against newer kernels (>=2.6.20), this allows one to setup or continue to run gfs1 with updated software that is currently not available in portage. It just happens to also be the software that supports gfs2. If people are feeling courageous they can go nuts with gfs2, but I'm sticking with gfs1 and cluster-2.x software for the foreseeable future.
All ebuilds, that fetch cluster-2.02.00.tar.gz, fail digest verification. ('Filesize does not match recorded size', 1764851, 8316680) !!! Fetched file: cluster-2.02.00.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 1764851 !!! Expected: 8316680 Also, cman-2.02.00 does not compile with sys-cluster/openais-0.82 due to missing openais/service/print.h. Downgrading to sys-cluster/openais-0.80.3 helps.
Is there any particular reason, why gfs2 tools (gfs2_mkfs...) are excluded from gfs-2.02.00.ebuild? To test gfs2 it would be nice to have them included.
(In reply to comment #18) > Also, cman-2.02.00 does not compile with sys-cluster/openais-0.82 due to > missing openais/service/print.h. Downgrading to sys-cluster/openais-0.80.3 > helps. The cluster-suite wiki actually says that 2.02.00 is compatible with openais-0.80.3. Whether that means only compatible with or not I don't know, but I agree the ebuild should accept anything >=openais-0.80.3 (In reply to comment #18) > Is there any particular reason, why gfs2 tools (gfs2_mkfs...) are excluded > from gfs-2.02.00.ebuild? To test gfs2 it would be nice to have them included. They're different filesystems. If anything a gfs2-2.02.00.ebuild should be created. I posted a link in the forums topic linked above that has some ebuilds for the 2.01.00 series that can be adapted pretty easily. I'm not maintaining them anymore since newer ones are in portage and I've ditched gfs in favor of ocfs2, but they are more up to date than the tar I posted in this bug.
hi, the problem still there, please someone fix it. thanks. 2008-09-04 16:02:23 (257 KB/s) - `/usr/portage/distfiles/cluster-2.02.00.tar.gz' saved [1764851] ('Filesize does not match recorded size', 1764851L, 8316680) !!! Fetched file: cluster-2.02.00.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 1764851 !!! Expected: 8316680 Refetching... File renamed to '/usr/portage/distfiles/cluster-2.02.00.tar.gz._checksum_failure_.P75t2t'
RH initially released a different package. now 2.02.xx is not anymore in portage, please test the last ebuild.
