Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DRBD: Users

DRDB Failover Not Right - Not Replicating Share

 

 

DRBD users RSS feed   Index | Next | Previous | View Threaded


chrissychalm at hotmail

Dec 26, 2011, 1:56 PM

Post #1 of 4 (444 views)
Permalink
DRDB Failover Not Right - Not Replicating Share

Hi,

Please help me!

I have my DRBD setup with two nodes, using software raid for storage as
/dev/md0.

I have followed these instructions
http://www.howtoforge.com/openfiler-2.99-active-passive-with-corosync-pacemaker-and-drbd.
Same LVM being /dev/data/filer. I then made a share called VMs and attached
it in ESXi with some files copied to it for testing.

The problem is that when I fail over my primary node, the new share that I
created didn't move. The /data/filer is made but not the share below it.
Whats going wrong? What am I missing?

I have tried:
- Invalidating the secondary node and letting everything copy across
- Running vgscan after changing the filter in /etc/lvm/lvm.conf (as
instructed)

When I then bring my primary back online the share is still there with the
files so hasn't been deleted or anything.

I have searched online and also on here but can't find anything.

Really appreciate it if you could help me :-(

--
View this message in context: http://old.nabble.com/DRDB-Failover-Not-Right---Not-Replicating-Share-tp33039171p33039171.html
Sent from the DRBD - User mailing list archive at Nabble.com.

_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


chrissychalm at hotmail

Dec 26, 2011, 12:13 PM

Post #2 of 4 (418 views)
Permalink
DRDB Failover Not Right - Not Replicating Share [In reply to]

Hi,

Please help me!

I have my DRBD setup with two nodes, using software raid for storage as
/dev/md0.

I have followed these instructions
http://www.howtoforge.com/openfiler-2.99-active-passive-with-corosync-pacemaker-and-drbd.
Same LVM being /dev/data/filer. I then made a share called VMs and attached
it in ESXi with some files copied to it for testing.

The problem is that when I fail over my primary node, the new share that I
created didn't move. The /data/filer is made but not the share below it.
Whats going wrong? What am I missing?

I have tried:
- Invalidating the secondary node and letting everything copy across
- Running vgscan after changing the filter in /etc/lvm/lvm.conf (as
instructed)

When I then bring my primary back online the share is still there with the
files so hasn't been deleted or anything.

I have searched online and also on here but can't find anything.

Really appreciate it if you could help me :-(

--
View this message in context: http://old.nabble.com/DRDB-Failover-Not-Right---Not-Replicating-Share-tp33039171p33039171.html
Sent from the DRBD - User mailing list archive at Nabble.com.

_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


lars.ellenberg at linbit

Dec 28, 2011, 4:24 AM

Post #3 of 4 (418 views)
Permalink
Re: DRDB Failover Not Right - Not Replicating Share [In reply to]

On Mon, Dec 26, 2011 at 01:56:15PM -0800, chalmc80 wrote:
>
> Hi,
>
> Please help me!
>
> I have my DRBD setup with two nodes, using software raid for storage as
> /dev/md0.
>
> I have followed these instructions
> http://www.howtoforge.com/openfiler-2.99-active-passive-with-corosync-pacemaker-and-drbd.
> Same LVM being /dev/data/filer. I then made a share called VMs and attached
> it in ESXi with some files copied to it for testing.
>
> The problem is that when I fail over my primary node, the new share that I
> created didn't move. The /data/filer is made but not the share below it.
> Whats going wrong? What am I missing?
>
> I have tried:
> - Invalidating the secondary node and letting everything copy across
> - Running vgscan after changing the filter in /etc/lvm/lvm.conf (as
> instructed)
>
> When I then bring my primary back online the share is still there with the
> files so hasn't been deleted or anything.

Then most likely the data you think you are replicating
is actually not even on DRBD?

Forgot to activate the vg after switchover?

What says
vgdisplay -vvv

> I have searched online and also on here but can't find anything.
>
> Really appreciate it if you could help me :-(

--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user


chrissychalm at hotmail

Dec 30, 2011, 3:50 AM

Post #4 of 4 (397 views)
Permalink
Re: DRDB Failover Not Right - Not Replicating Share [In reply to]

Ive had a look at the problem you suggested with activating the VG but I
don't think its that. When I fail over I can only see /dev/data/filer
instead of /dev/data/filer/vms which is on my Master.

I can't give you a print out of vgdisplay -vvv just now, another problem
seems to have cropped up.

I wanted to re-make my Volume Groups to see if it was that and made another
problem. When re-making it didn't work so looked into it further.

Ive ran these commands in order (below) and now it won't failover correctly:
:-((
vgchange –a n <volume group name>
vgremove <volume group name>
pvscan
pvremove /dev/drbd1
pvcreate /dev/drbd1
vgcreate data /dev/drbd1
lvcreate -L 400M -n filer data

What other things could be causing only the share not to display? Would
using software RAID /dev/md0 be anything to do with it?


On Mon, Dec 26, 2011 at 01:56:15PM -0800, chalmc80 wrote:
>
> Hi,
>
> Please help me!
>
> I have my DRBD setup with two nodes, using software raid for storage as
> /dev/md0.
>
> I have followed these instructions
> http://www.howtoforge.com/openfiler-2.99-active-passive-with-corosync-pacemaker-and-drbd.
> Same LVM being /dev/data/filer. I then made a share called VMs and
> attached
> it in ESXi with some files copied to it for testing.
>
> The problem is that when I fail over my primary node, the new share that I
> created didn't move. The /data/filer is made but not the share below it.
> Whats going wrong? What am I missing?
>
> I have tried:
> - Invalidating the secondary node and letting everything copy across
> - Running vgscan after changing the filter in /etc/lvm/lvm.conf (as
> instructed)
>
> When I then bring my primary back online the share is still there with the
> files so hasn't been deleted or anything.

Then most likely the data you think you are replicating
is actually not even on DRBD?

Forgot to activate the vg after switchover?

What says
vgdisplay -vvv
--
View this message in context: http://old.nabble.com/DRDB-Failover-Not-Right---Not-Replicating-Share-tp33039171p33054352.html
Sent from the DRBD - User mailing list archive at Nabble.com.

_______________________________________________
drbd-user mailing list
drbd-user [at] lists
http://lists.linbit.com/mailman/listinfo/drbd-user

DRBD users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.