From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [Linux-cluster] hi,question about gfs2
Date: Tue, 22 Feb 2011 08:48:42 -0500 (EST) [thread overview]
Message-ID: <205773825.125610.1298382522204.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <6d94d69.12d04.12e4b5362f4.Coremail.ooolinux@163.com>
----- Original Message -----
| 1.if i can deploy gfs2 on fedora12. if it is ok to build from source
| code ?
Yes you can. However, as Andrew said, it's probably a mistake.
You're better off using Fedora 14 where the code base is newer
and it will be supported longer.
You can build it from source, but find a source that's compatible
with your kernel may be a challenge. GFS2 has advanced to match
ongoing kernel development.
You can build the Fedora 12 kernel from source RPMS, but you're
likely going to encounter bugs that have already been fixed by
later revisions.
If you go with Fedora 14, it may be easier to compile the latest
source from the GFS2 kernel git repo.
| 2.the max node gfs2 can manger? i use san, if i have 100 machines,if
| gfs2 can work over those nodes?
|
| thanks
GFS2 does not care how many nodes are in your cluster.
The only thing that cares is the rest of the cluster infrastructure.
However, we don't recommend that many nodes for various reasons.
For one thing, your network may be clogged with lots of traffic,
which may interfere with proper cluster communications.
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2011-02-22 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 3:04 [Cluster-devel] hi,question about gfs2 yue
2011-02-22 13:48 ` Bob Peterson [this message]
[not found] <AANLkTin+Nbvp3P+zfZMegXXBhi3dXV-GrRfTW9UZuauw@mail.gmail.com>
[not found] ` <30cb8ebe.1293c.12e4b4a8e15.Coremail.ooolinux@163.com>
2011-02-23 1:59 ` [Cluster-devel] [Linux-cluster] " yue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=205773825.125610.1298382522204.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
--to=rpeterso@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).