Hello Lon the rest of the list - You responded the other day that my
problem with the ext3 volume mounting up on multiple nodes might be related
to this bug listed.
Support looked over my config and explained to me that I nested my resources
when I really shouldn't have. They say the cluster
On Tue, 2007-10-30 at 15:07 -0400, Josh Gray wrote:
You asked me that a while back, pardon my inexperience with Linux thus far
not positive how to get the version numbers you're looking for.
Here's a few -
# uname -a
Linux nfs-5.cdc.nicusa.com 2.6.18-8.1.15.el5 #1 SMP Thu Oct 4 04:06:39
Hmmm I don't see to have access to that bug after creating an account. Can
you summarize or cut/paste some info?
Josh
On 10/31/07 10:16 AM, Lon Hohberger [EMAIL PROTECTED] wrote:
On Tue, 2007-10-30 at 15:07 -0400, Josh Gray wrote:
You asked me that a while back, pardon my inexperience with
Interesting, thanks. I'll mention this to support. I'm sure they can find
other ways to improve my increasingly ugly config though too!
Josh
On 10/31/07 12:55 PM, Lon Hohberger [EMAIL PROTECTED] wrote:
On Wed, 2007-10-31 at 11:56 -0600, Josh Gray wrote:
Hmmm I don't see to have access to
On Mon, 2007-10-29 at 11:02 -0400, Josh Gray wrote:
Lon and the other gurus - have you guys ever seen an ext3 volume get mounted
on multiple cluster nodes at the same time WITHOUT a split brain? No
fencing, no errors logged, no network issues, etc.. I even ran clustat and
both nodes (let's
You asked me that a while back, pardon my inexperience with Linux thus far
not positive how to get the version numbers you're looking for.
Here's a few -
# uname -a
Linux nfs-5.cdc.nicusa.com 2.6.18-8.1.15.el5 #1 SMP Thu Oct 4 04:06:39 EDT
2007 x86_64 x86_64 x86_64 GNU/Linux
# cman_tool
On Mon, 29 Oct 2007, Josh Gray wrote:
Lon and the other gurus - have you guys ever seen an ext3 volume get mounted
on multiple cluster nodes at the same time WITHOUT a split brain? No
fencing, no errors logged, no network issues, etc.. I even ran clustat and
both nodes (let's say B and C )
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Sure, that works. The only problem is that if both nodes write to the
same files at the same time (including meta data), you'll end up with a
corrupted file system. But if both machines are mounting the FS
read-only (in
On Mon, 29 Oct 2007, Bryn M. Reeves wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Sure, that works. The only problem is that if both nodes write to the
same files at the same time (including meta data), you'll end up with a
corrupted file system. But if both
I can tell you for a fact that is what happened unfortunately.Two nodes
of 3 became active and were quite content to serve my NFS traffic on
multiple VIPs and write to the same EXT3 volume for about 20 or so minutes
until it went read only.
Most frustrating part of the whole deal was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
On Mon, 29 Oct 2007, Bryn M. Reeves wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
Sure, that works. The only problem is that if both nodes write to the
same files at the same time
Heh oh yea I understand all of that about EXT3.. It's in the cluster
configuration, not mounting thru fstab.
Josh
On 10/29/07 11:47 AM, Bryn M. Reeves [EMAIL PROTECTED] wrote:
Are you sure about that? I've never known it do anything useful beyond
spectacularly breaking the file systems
12 matches
Mail list logo
