Hi,
Linus pulled the -fixes tree last night, so I'm just about to rebase
both GFS2 git trees to the new upstream kernel,
Steve.
Hi,
Thanks for the patch. I've pushed it into the GFS2 -fixes tree,
Steve.
On Tue, 2010-01-12 at 03:36 +0900, OGAWA Hirofumi wrote:
If -follow_link handler return the error, it should decrement
nd-path refcnt.
This patch fix it.
Signed-off-by: OGAWA Hirofumi hirof...@mail.parknet.co.jp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The cluster team and its community are proud to announce the 3.0.7
stable release from the STABLE3 branch.
This release contains a few major bug fixes. We strongly recommend
people to update your clusters.
In order to build/run the 3.0.7 release you
Hi all,
as previously announced, STABLE2 tree is now to be considered deprecated
and unsupported.
the STABLE2 branch in git has been marked read-only and no more
cluster-2 releases will take place.
Cheers
Fabio
Hello Fabio,
hello list,
Am Dienstag, den 12.01.2010, 12:16 +0100 schrieb Fabio M. Di Nitto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The cluster team and its community are proud to announce the 3.0.7
stable release from the STABLE3 branch.
This release contains a few major bug
Hi Marc,
On 1/12/2010 3:10 PM, Marc - A. Dahlhaus [ Administration | Westermann
GmbH ] wrote:
- - linux kernel 2.6.31
gfs-kernel doesn't build against 2.6.32 without the following (untested)
change:
sed 's/generic_file_aio_write_nolock/blkdev_aio_write/' \
-i
I just discovered that the cpg group names that fenced, dlm_controld and
gfs_controld use in cluster3 include a nul within the name length. This
can happen because cpg names have both a string part and a length part,
and the length is currently being set to strlen + 1 instead of strlen.
It's
David,
How about making corosync-cpgtool default to the -e behavior, and making
-e = escape unprintable characters in group name ?
This can be done quickly, but I don't understand what is that good for
and how does it help. Internally (in cpg exec) names are compared with
full length. This
Hi Lon, Chrissie, and the rest of the team ;-)
I'm going through my list of uh-oh, this is missing issues, and I
noticed that I have a fairly strong need for disk-based quorum.
I wonder what the current state/roadmap is, and how one could help?
Regards,
Lars
--
Architect Storage/HA, OPS
