headers
Corey Kovacs | 1 May 2011 11:32
Picon

Re: How do you HA your storage?

You could probably do what you want using san level mirroring across
two sans and device-mapper-multipath. I believe the sans will
automatically put the alternate san copies into read/write if it
cannot communicate with the first if it's configured to do so but I
don't have access to that capability on my EVA for lack of license.
Actually, it woulnd't require a whole other san but if I was mirroring
things, that's what I'd opt for. This is the kind of problem that DMP
was designed to handle. If you are booting from the san, you may have
some other tweeks but in general I think DMP is still the way to go.

Good luck

-C

On Sat, Apr 30, 2011 at 6:00 PM, urgrue <urgrue <at> bulbous.org> wrote:
> On 30/4/11 14:27, Corey Kovacs wrote:
>
> This has nothing to do with any network. It's all over the fiber...
>
> True, my bad, I was thinking of DRBD.
>
>> Points in time? It's a raid 1, it's relatively instant. It's more
>> complex to manage a failover in the way you describe if anything.
>
> I didn't mean that. What I meant is with any enterprise storage filer I can
> walk in and take a point in time snapshot of my entire datacenter - all
> hundreds of servers - with almost no effort. And restore it. That's a pretty
> fantastic thing to be able to do before, say, a major upgrade on hundreds of
> servers. And you manage all of it in one place. Take a situation like if the
> company decides it needs a third copy of the data. It'd be a fun job to map
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jankowski, Chris | 1 May 2011 13:22
Picon
Favicon

Re: How do you HA your storage?

I think you might not appreciate subtleties involved in making the decision of failover and concurrency
issues between different LUNs.

Be that as it may, I'd suggest to close this discussion at this point, as it has nothing to do with the Linux
cluster and everything to do with general BC and DR in multi-site environment.  There are specialized
forums for this.

Regards,

Chris

-----Original Message-----
From: urgrue [mailto:urgrue <at> bulbous.org] 
Sent: Sunday, 1 May 2011 02:42
To: linux clustering
Cc: Jankowski, Chris
Subject: Re: [Linux-cluster] How do you HA your storage?

I do have RAID, multipath over multiple fabrics, etc. But what you're 
not at all protected from is major SAN failure, or a datacenter outage, 
for example. Which happens, and if you've got more than a few 
datacenters and dozens of SAN filers, you know they happen actually way 
too often for you to not miss a graceful, predictable recovery procedure.

So like everyone else, you've got cluster nodes in each datacenter, and 
all of them connected to the same SAN. Everything will recover quite 
nicely from just about every type of failure - except failure of the SAN 
itself. Your cluster nodes in your backup datacenter will not be happy 
to see the disks disappear. You can activate your backup filer(s) in 
seconds - all your hundreds of passive nodes actually do now have
(Continue reading)

Permalink | Reply | 0 comments |
headers
Karadeniz, Ercan, VF-Group | 1 May 2011 23:57

GFS2 daemon hangs during boot process

Hi Linux-Cluster-List-Members,

 

I’m a newbie in RHCS. I have visited recently the RH436 training. Currently I’m trying to get more experience by doing some hands-on on the course labs.

 

My setup is as follows:

·         Physical Server where Dom-0 is running

·         2 x xen virtual machines

·         2 nodes cluster (via Conga)

 

The two node cluster is setup by using Conga. The node1 and node2 are xen virtual machines. Everything worked so far. For fencing I’m using fence_xvmd. That is also working without any problems.

To test the multicasting with different address (than the default one), I have done some changes on the multicast address and rebooted both nodes. Apparently when I start node1 or node2 (xm console node1 –c ) they hang during boot process on the “GFS2 daemon”.

I have tried to login via using the “Single” mode as boot parameter regrettably this didn’t help.

 

My question is how can I overcome this deadlock situation. I need somehow to boot both nodes and change my recent changes related to the multicasting address in the cluster.conf file. However I cannot login to any of the nodes? Furthermore is there a change within the xen virtual machine to get in to the interactive boot mode?

 

It would be great if you can give me some hint here.

 

Many thanks in advance!

 

Warm regards from Düsseldorf/Germany

 

Ercan Karadeniz

 

 

<div><div class="WordSection1">
<p class="MsoNormal">Hi Linux-Cluster-List-Members,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I&rsquo;m a newbie in RHCS. I have visited recently the RH436 training. Currently I&rsquo;m trying to get more experience by doing some hands-on on the course labs.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">My setup is as follows:<p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>Physical Server where Dom-0 is running<p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>2 x xen virtual machines<p></p></p>
<p class="MsoListParagraph"><span><span>&middot;<span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span>2 nodes cluster (via Conga)<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">The two node cluster is setup by using Conga. The node1 and node2 are xen virtual machines. Everything worked so far. For fencing I&rsquo;m using fence_xvmd. That is also working without any problems. <p></p></p>
<p class="MsoNormal">To test the multicasting with different address (than the default one), I have done some changes on the multicast address and rebooted both nodes. Apparently when I start node1 or node2 (xm console node1 &ndash;c ) they hang during boot process on the &ldquo;GFS2 daemon&rdquo;.<p></p></p>
<p class="MsoNormal">I have tried to login via using the &ldquo;Single&rdquo; mode as boot parameter regrettably this didn&rsquo;t help.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">My question is how can I overcome this deadlock situation. I need somehow to boot both nodes and change my recent changes related to the multicasting address in the cluster.conf file. However I cannot login to any of the nodes? Furthermore is there a change within the xen virtual machine to get in to the interactive boot mode?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">It would be great if you can give me some hint here.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Many thanks in advance!<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Warm regards from D&uuml;sseldorf/Germany<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Ercan Karadeniz<p></p></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div></div>
Permalink | Reply | 2 comments |
headers
Digimer | 2 May 2011 00:09

Re: GFS2 daemon hangs during boot process

On 05/01/2011 05:57 PM, Karadeniz, Ercan, VF-Group wrote:
> Hi Linux-Cluster-List-Members,
> 
> I’m a newbie in RHCS. I have visited recently the RH436 training.
> Currently I’m trying to get more experience by doing some hands-on on
> the course labs.
> 
> My setup is as follows:
> 
> ·         Physical Server where Dom-0 is running
> ·         2 x xen virtual machines
> ·         2 nodes cluster (via Conga)
> 
> The two node cluster is setup by using Conga. The node1 and node2 are
> xen virtual machines. Everything worked so far. For fencing I’m using
> fence_xvmd. That is also working without any problems.
> 
> To test the multicasting with different address (than the default one),
> I have done some changes on the multicast address and rebooted both
> nodes. Apparently when I start node1 or node2 (xm console node1 –c )
> they hang during boot process on the “GFS2 daemon”.
> 
> I have tried to login via using the “Single” mode as boot parameter
> regrettably this didn’t help.
> 
> My question is how can I overcome this deadlock situation. I need
> somehow to boot both nodes and change my recent changes related to the
> multicasting address in the cluster.conf file. However I cannot login to
> any of the nodes? Furthermore is there a change within the xen virtual
> machine to get in to the interactive boot mode?
> 
> It would be great if you can give me some hint here.
> 
> Many thanks in advance!

You could try booting the VM using the RHEL5 ISO as the first boot
device, then boot into rescue mode. This should allow you to mount the
system and edit you /etc/fstab and/or /etc/cluster/cluster.conf.

As a side note, for testing, I like to 'chkconfig cman off'. This way, I
know that even if I totally screw up, I'll always be able to boot into
the host OS. :)

Further, I'd set the GFS2 entry in fstab to not use 'defaults', but
instead to use 'rw,suid,dev,exec,nouser,async'. This excludes the 'auto'
option, so that a failure to mount the GFS2 partition won't cause dom0
to drop to single-user mode.

--

-- 
Digimer
E-Mail: digimer <at> alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org
Permalink | Reply | 1 comment |
headers
Marek Grac | 2 May 2011 09:33
Picon
Favicon

Re: Plugged out blade from bladecenter chassis - fence_bladecenter failed

Hi,

On 04/29/2011 10:15 AM, Parvez Shaikh wrote:
> Hi Marek,
>
> Can we give this option in cluster.conf file for bladecenter fencing 
> device or method

for cluster.conf you should add ... missing_as_off="1" ... to fence 
configuration

>
> For IPMI, fencing is there similar option?
>

There is no such method for IPMI.

m,
Permalink | Reply | 2 comments |
headers
Karadeniz, Ercan, VF-Group | 2 May 2011 13:35

Re: GFS2 daemon hangs during boot process

Many thanks for the hints.

Regards,
Ercan

-----Original Message-----
From: Digimer [mailto:linux <at> alteeve.com] 
Sent: Montag, 2. Mai 2011 00:09
To: linux clustering
Cc: Karadeniz, Ercan, VF-Group
Subject: Re: [Linux-cluster] GFS2 daemon hangs during boot process

On 05/01/2011 05:57 PM, Karadeniz, Ercan, VF-Group wrote:
> Hi Linux-Cluster-List-Members,
> 
> I'm a newbie in RHCS. I have visited recently the RH436 training.
> Currently I'm trying to get more experience by doing some hands-on on 
> the course labs.
> 
> My setup is as follows:
> 
> *         Physical Server where Dom-0 is running
> *         2 x xen virtual machines
> *         2 nodes cluster (via Conga)
> 
> The two node cluster is setup by using Conga. The node1 and node2 are 
> xen virtual machines. Everything worked so far. For fencing I'm using 
> fence_xvmd. That is also working without any problems.
> 
> To test the multicasting with different address (than the default 
> one), I have done some changes on the multicast address and rebooted 
> both nodes. Apparently when I start node1 or node2 (xm console node1 
> -c ) they hang during boot process on the "GFS2 daemon".
> 
> I have tried to login via using the "Single" mode as boot parameter 
> regrettably this didn't help.
> 
> My question is how can I overcome this deadlock situation. I need 
> somehow to boot both nodes and change my recent changes related to the

> multicasting address in the cluster.conf file. However I cannot login 
> to any of the nodes? Furthermore is there a change within the xen 
> virtual machine to get in to the interactive boot mode?
> 
> It would be great if you can give me some hint here.
> 
> Many thanks in advance!

You could try booting the VM using the RHEL5 ISO as the first boot
device, then boot into rescue mode. This should allow you to mount the
system and edit you /etc/fstab and/or /etc/cluster/cluster.conf.

As a side note, for testing, I like to 'chkconfig cman off'. This way, I
know that even if I totally screw up, I'll always be able to boot into
the host OS. :)

Further, I'd set the GFS2 entry in fstab to not use 'defaults', but
instead to use 'rw,suid,dev,exec,nouser,async'. This excludes the 'auto'
option, so that a failure to mount the GFS2 partition won't cause dom0
to drop to single-user mode.

--
Digimer
E-Mail: digimer <at> alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org
Permalink | Reply | 0 comments |
headers
Parvez Shaikh | 2 May 2011 15:19
Picon

Re: Plugged out blade from bladecenter chassis - fence_bladecenter failed

Hi Marek,

I tried the option missing_as_off="1" and now I get an another error -

fenced[18433]: fence "node5.sscdomain" failed
fenced[18433]: fencing node "node5.sscdomain"

Sniplet of cluster.conf file is -
....
    <clusternode name="node5" nodeid="5" votes="1">
      <fence>
        <method name="1">
          <device blade="5" name="BladeCenterFencing" missing_as_off="1"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
....
  <fencedevices>
    <fencedevice agent="fence_bladecenter" ipaddr="blade-mm-1" login="USERID" name="BladeCenterFencing" passwd="PASSW0RD"/>
  </fencedevices>

Did I miss something?

Thanks
Parvez


On Mon, May 2, 2011 at 1:03 PM, Marek Grac <mgrac <at> redhat.com> wrote:
Hi,


On 04/29/2011 10:15 AM, Parvez Shaikh wrote:
Hi Marek,

Can we give this option in cluster.conf file for bladecenter fencing device or method

for cluster.conf you should add ... missing_as_off="1" ... to fence configuration



For IPMI, fencing is there similar option?


There is no such method for IPMI. 

<div>
<p>Hi Marek,<br><br>I tried the option missing_as_off="1" and now I get an another error - <br><br>fenced[18433]: fence "node5.sscdomain" failed<br>fenced[18433]: fencing node "node5.sscdomain"<br><br>Sniplet of cluster.conf file is -<br>....<br>&nbsp;&nbsp;&nbsp; &lt;clusternode name="node5" nodeid="5" votes="1"&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;fence&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;method name="1"&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;device blade="5" name="BladeCenterFencing" missing_as_off="1"/&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/method&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/fence&gt;<br>&nbsp;&nbsp;&nbsp; &lt;/clusternode&gt;<br>&nbsp; &lt;/clusternodes&gt;<br>....<br>&nbsp; &lt;fencedevices&gt;<br>&nbsp;&nbsp;&nbsp; &lt;fencedevice agent="fence_bladecenter" ipaddr="blade-mm-1" login="USERID" name="BladeCenterFencing" passwd="PASSW0RD"/&gt;<br>
&nbsp; &lt;/fencedevices&gt;<br><br>Did I miss something?<br><br>Thanks<br>Parvez<br><br><br></p>
<div class="gmail_quote">On Mon, May 2, 2011 at 1:03 PM, Marek Grac <span dir="ltr">&lt;<a href="mailto:mgrac <at> redhat.com">mgrac <at> redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">Hi,<div class="im">
<br><br>
On 04/29/2011 10:15 AM, Parvez Shaikh wrote:<br><blockquote class="gmail_quote">
Hi Marek,<br><br>
Can we give this option in cluster.conf file for bladecenter fencing device or method<br>
</blockquote>
<br>
</div>
for cluster.conf you should add ... missing_as_off="1" ... to fence configuration<div class="im">
<br><br><blockquote class="gmail_quote">
<br>
For IPMI, fencing is there similar option?<br><br>
</blockquote>
<br>
</div>
There is no such method for IPMI.<div>
<div></div>
<div class="h5">
<br><br>
m,<br><br>
--<br>
Linux-cluster mailing list<br><a href="mailto:Linux-cluster <at> redhat.com" target="_blank">Linux-cluster <at> redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/linux-cluster" target="_blank">https://www.redhat.com/mailman/listinfo/linux-cluster</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
Permalink | Reply | 1 comment |
headers
Digimer | 4 May 2011 17:37

GFS2 partition grew with 'gfs2_grow -T'

This is a little concerning... Can someone confirm that I didn't screw
up before I lodge a bug?

[root <at> xenmaster003 ~]# rpm -q cman gfs2-utils
cman-2.0.115-68.el5_6.3
gfs2-utils-0.1.62-28.el5

[root <at> xenmaster003 ~]# lvextend -L +50G /dev/drbd_sh1_vg0/cluster_files
/dev/drbd3
  Extending logical volume cluster_files to 250.00 GB
  Logical volume cluster_files successfully resized
[root <at> xenmaster003 ~]# gfs2_grow -T /dev/drbd_sh1_vg0/cluster_files
/cluster_files/
(Test mode--File system will not be changed)
FS: Mount Point: /cluster_files
FS: Device:      /dev/mapper/drbd_sh1_vg0-cluster_files
FS: Size:        52428798 (0x31ffffe)
FS: RG size:     65535 (0xffff)
DEV: Size:       65536000 (0x3e80000)
The file system grew by 51200MB.
FS: Mount Point: /cluster_files
FS: Device:      /dev/mapper/drbd_sh1_vg0-cluster_files
FS: Size:        52428798 (0x31ffffe)
FS: RG size:     65535 (0xffff)
DEV: Size:       65536000 (0x3e80000)
The file system grew by 51200MB.
gfs2_grow complete.

[root <at> xenmaster003 ~]# gfs2_grow /dev/drbd_sh1_vg0/cluster_files
/cluster_files/
FS: Mount Point: /cluster_files
FS: Device:      /dev/mapper/drbd_sh1_vg0-cluster_files
FS: Size:        52428798 (0x31ffffe)
FS: RG size:     65535 (0xffff)
DEV: Size:       65536000 (0x3e80000)
The file system grew by 51200MB.
Error: The device has grown by less than one Resource Group (RG).
The device grew by 0MB.  One RG is 255MB for this file system.
gfs2_grow complete.

[root <at> xenmaster003 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md2               57G  2.7G   51G   6% /
/dev/md0              251M   52M  187M  22% /boot
tmpfs                 7.7G     0  7.7G   0% /dev/shm
/dev/mapper/drbd_sh0_vg0-xen_shared
                       56G  259M   56G   1% /xen_shared
/dev/mapper/drbd_sh1_vg0-cluster_files
                      250G  145G  106G  58% /cluster_files

--

-- 
Digimer
E-Mail: digimer <at> alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org
Permalink | Reply | 3 comments |
headers
Bob Peterson | 4 May 2011 17:54
Picon
Favicon

Re: GFS2 partition grew with 'gfs2_grow -T'

----- Original Message -----
| This is a little concerning... Can someone confirm that I didn't screw
| up before I lodge a bug?
| 
| [root <at> xenmaster003 ~]# rpm -q cman gfs2-utils
| cman-2.0.115-68.el5_6.3
| gfs2-utils-0.1.62-28.el5
| 
| [root <at> xenmaster003 ~]# lvextend -L +50G
| /dev/drbd_sh1_vg0/cluster_files
| /dev/drbd3
| Extending logical volume cluster_files to 250.00 GB
| Logical volume cluster_files successfully resized
| [root <at> xenmaster003 ~]# gfs2_grow -T /dev/drbd_sh1_vg0/cluster_files
| /cluster_files/
| (Test mode--File system will not be changed)
| FS: Mount Point: /cluster_files
| FS: Device: /dev/mapper/drbd_sh1_vg0-cluster_files
| FS: Size: 52428798 (0x31ffffe)
| FS: RG size: 65535 (0xffff)
| DEV: Size: 65536000 (0x3e80000)
| The file system grew by 51200MB.
| FS: Mount Point: /cluster_files
| FS: Device: /dev/mapper/drbd_sh1_vg0-cluster_files
| FS: Size: 52428798 (0x31ffffe)
| FS: RG size: 65535 (0xffff)
| DEV: Size: 65536000 (0x3e80000)
| The file system grew by 51200MB.
| gfs2_grow complete.
| 
| [root <at> xenmaster003 ~]# gfs2_grow /dev/drbd_sh1_vg0/cluster_files
| /cluster_files/
| FS: Mount Point: /cluster_files
| FS: Device: /dev/mapper/drbd_sh1_vg0-cluster_files
| FS: Size: 52428798 (0x31ffffe)
| FS: RG size: 65535 (0xffff)
| DEV: Size: 65536000 (0x3e80000)
| The file system grew by 51200MB.
| Error: The device has grown by less than one Resource Group (RG).
| The device grew by 0MB. One RG is 255MB for this file system.
| gfs2_grow complete.
| 
| [root <at> xenmaster003 ~]# df -h
| Filesystem Size Used Avail Use% Mounted on
| /dev/md2 57G 2.7G 51G 6% /
| /dev/md0 251M 52M 187M 22% /boot
| tmpfs 7.7G 0 7.7G 0% /dev/shm
| /dev/mapper/drbd_sh0_vg0-xen_shared
| 56G 259M 56G 1% /xen_shared
| /dev/mapper/drbd_sh1_vg0-cluster_files
| 250G 145G 106G 58% /cluster_files
| 
| --
| Digimer
| E-Mail: digimer <at> alteeve.com
| AN!Whitepapers: http://alteeve.com
| Node Assassin: http://nodeassassin.org

Hi,

Hm...This sounds like a bug to me.  I'd open the bug record.

Regards,

Bob Peterson
Red Hat File Systems
Permalink | Reply | 2 comments |
headers
Digimer | 4 May 2011 17:59

Re: GFS2 partition grew with 'gfs2_grow -T'

On 05/04/2011 11:54 AM, Bob Peterson wrote:
> ----- Original Message -----
> | This is a little concerning... Can someone confirm that I didn't screw
> | up before I lodge a bug?
> | 
> | [root <at> xenmaster003 ~]# rpm -q cman gfs2-utils
> | cman-2.0.115-68.el5_6.3
> | gfs2-utils-0.1.62-28.el5
> | 
> | [root <at> xenmaster003 ~]# lvextend -L +50G
> | /dev/drbd_sh1_vg0/cluster_files
> | /dev/drbd3
> | Extending logical volume cluster_files to 250.00 GB
> | Logical volume cluster_files successfully resized
> | [root <at> xenmaster003 ~]# gfs2_grow -T /dev/drbd_sh1_vg0/cluster_files
> | /cluster_files/
> | (Test mode--File system will not be changed)
> | FS: Mount Point: /cluster_files
> | FS: Device: /dev/mapper/drbd_sh1_vg0-cluster_files
> | FS: Size: 52428798 (0x31ffffe)
> | FS: RG size: 65535 (0xffff)
> | DEV: Size: 65536000 (0x3e80000)
> | The file system grew by 51200MB.
> | FS: Mount Point: /cluster_files
> | FS: Device: /dev/mapper/drbd_sh1_vg0-cluster_files
> | FS: Size: 52428798 (0x31ffffe)
> | FS: RG size: 65535 (0xffff)
> | DEV: Size: 65536000 (0x3e80000)
> | The file system grew by 51200MB.
> | gfs2_grow complete.
> | 
> | [root <at> xenmaster003 ~]# gfs2_grow /dev/drbd_sh1_vg0/cluster_files
> | /cluster_files/
> | FS: Mount Point: /cluster_files
> | FS: Device: /dev/mapper/drbd_sh1_vg0-cluster_files
> | FS: Size: 52428798 (0x31ffffe)
> | FS: RG size: 65535 (0xffff)
> | DEV: Size: 65536000 (0x3e80000)
> | The file system grew by 51200MB.
> | Error: The device has grown by less than one Resource Group (RG).
> | The device grew by 0MB. One RG is 255MB for this file system.
> | gfs2_grow complete.
> | 
> | [root <at> xenmaster003 ~]# df -h
> | Filesystem Size Used Avail Use% Mounted on
> | /dev/md2 57G 2.7G 51G 6% /
> | /dev/md0 251M 52M 187M 22% /boot
> | tmpfs 7.7G 0 7.7G 0% /dev/shm
> | /dev/mapper/drbd_sh0_vg0-xen_shared
> | 56G 259M 56G 1% /xen_shared
> | /dev/mapper/drbd_sh1_vg0-cluster_files
> | 250G 145G 106G 58% /cluster_files
> | 
> | --
> | Digimer
> | E-Mail: digimer <at> alteeve.com
> | AN!Whitepapers: http://alteeve.com
> | Node Assassin: http://nodeassassin.org
> 
> Hi,
> 
> Hm...This sounds like a bug to me.  I'd open the bug record.
> 
> Regards,
> 
> Bob Peterson
> Red Hat File Systems

Will do, thanks for the prompt reply.

--

-- 
Digimer
E-Mail: digimer <at> alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org
Permalink | Reply | 0 comments |

Gmane