Thread: AW: [SSI-users] DRBD
Brought to you by:
brucewalker,
rogertsang
From: Stefan F. <St...@fu...> - 2005-01-29 22:00:19
|
Hi, I saw such drbd discribtion for debian the first time. I try that, But then I can't boot: Starting drbd ressource: mount: special device /dev/drbd/0 does not = exist. ERROR: mounting root file system failed Unable to continue. Halting. How can I create the devices?? I tried it with MAKEDEV but no success. How is the looking of fstab?? I dont have an uuid entry!!! Where is my failure?? Tia stefan =20 > -----Urspr=FCngliche Nachricht----- > Von: ssi...@li...=20 > [mailto:ssi...@li...] Im=20 > Auftrag von Everett Coleman II > Gesendet: Samstag, 29. Januar 2005 17:52 > An: Shaun Martin > Cc: ssi-users > Betreff: Re: [SSI-users] DRBD >=20 > hello shaun, >=20 > it's a hell of a lot easier if you have the ssi cluster=20 > installed and running before you setup drbd!!!!! trust me ;) >=20 > the drbd failover howto on openssi.org is a bit outdated.=20 > basically your going to follow the instructions on=20 > http://openssi.org/docs/rh/README.drbd.shtml, but with out=20 > the editing of the init files... >=20 >=20 > pre) start with just the init node, turn all others off >=20 > 1) apt-get install the drbd packages. > 2) edit the default drbd.conf, mine is attached. > 3) modprobe drbd, if you don't do this, the mkinitrd will=20 > fail cause it > can't find the drbd devices, ****** you should have no > warnings/errors with your config, if you do FIX THEM!!!!!!!!! > 4) add 'drbd' to /etc/mkinitrd/modules > 5) set 'DRBD_CONFIG=3Dyes' in /etc/mkinitrd/mkinitrd.conf > 6) replace UUID=3Df00barf00 with /dev/drbd/0 > 7) add 'drbd node=3D<comma separated list of initnodes> Y' to=20 > /etc/rc.nodeinfo > 8) be sure to use ssi-chnode to modify all nodes that will be drbd > failovers, make them initnodes > 9) you should be ready to make your initrd, issue ssi-ksync.... it's > easier and it puts them in the tftp directory and everywhere you'll > need it > 10) reboot, it should give you a error/warning about not having a > primary disk/node, when it prompts you for a shell, enter=20 > the shell and issue > drbdadm --do-what-I-say primary all, after you exit the shell it > should boot just fine. > 11) since you did ssi-ksync, you can boot the second intinode > 12) once the second node is up you can issue 'drbdsetup=20 > /dev/drbd/0 wait_sync' >=20 >=20 > I did this about two weeks ago, and i'm going purely off of=20 > my dead brain cells from drinking too much... so be sure to read: > http://openssi.org/docs/rh/README.drbd.shtml and > http://www.drbd.org/documentation.html instalation guid and quick > start guide, to get a feel of what you need to do... >=20 >=20 > On 2005-01-28 13:59:43, Shaun Martin wrote: > > Hi All, > >=20 > > Ok I have debian sarge with openssi1.2, ltsp and ha-lvs working as=20 > > well as my nfs on the CVIP address. Last thing I need to do=20 > is drbd. I=20 > > was wondering if anyone has a installation setup that works=20 > for debian. > >=20 > > Thanks, > > Shaun > >=20 > > -- > > --------------------- > > Shaun Martin > > Information Systems Administrator > > Aura Communications, Inc. > > 187 Ballardvale Street > > Wilmington, MA 01887 > > ------------------------------ > > Direct: 978.527.4133 > > Mobile: 978.360.3402 > > Main: 978.988.0088 x133 > > Fax: 978.988.3977 > > www.auracomm.com > >=20 > ---------------------------------------------------------------------- > >=20 > ---------------------------------------------------------------------- > > ------------------------ > >=20 > >=20 > >=20 > >=20 > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive=20 > > Reporting Tool for open source databases. Create=20 > drag-&-drop reports.=20 > > Save time by over 75%! Publish reports on the web. Export=20 > to DOC, XLS, RTF, etc. > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > > _______________________________________________ > > Ssic-linux-users mailing list > > Ssi...@li... > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > >=20 >=20 > --=20 > +--------------------------------------------------+ > |Everett Coleman II | > |http://ctech.fuzzyneural.net | > | | > |GnuPG Fingerprint: | > |E233 546E ED79 1D29 1D9D 04F0 DA5B 10F6 3FD3 DD12| > +--------------------------------------------------+ >=20 |
From: Stefan F. <St...@fu...> - 2005-02-27 03:08:07
|
I think it is a good idea to discuss it on the devel-list. I have the same problems. No failover with drbd, syncing seems to work, but no failover is possible ( power off the root node) the second node entering kdb>!! I try it since 3 month, now I give up and in the moment I try another solution.=20 When drbd is working with opennssi I surly come back. So long... stefan >=20 > In general you need both DRBD nodes in a Consistent state=20 > before doing failover. See /proc/drbd. Usually the first=20 > time you want to sync the entire root filesystem by issuing a=20 > --invalidate-remote on the node that has the good data. =20 > WARNING: If you issue the command on the wrong node you can=20 > destroy your entire root filesystem with no chance of recovery. >=20 > Also testing that you can boot cleanly from the failover DRBD=20 > node is a good idea, before you begin any failover tests. >=20 > One more thing DRBD-SSI code base is not as mature as SSI=20 > itself. That is why we supply this as an optional package=20 > separate from the main SSI release. Which DRBD-SSI patch are=20 > you using? Are you using the drbd-ssi-1.2.0.i686.tar.gz=20 > package? And which GNU/Linux distro are you using again? >=20 > I think at this stage as we get more technical on this=20 > DRBD-SSI topic, we can consider continuing this discussion on=20 > the SSI-devel list. >=20 > Thanks. >=20 > -Roger >=20 >=20 > > Now that I've got drbd running with openssi, what are some=20 > reasonable=20 > > failure tests to try to verify that this actually provides high=20 > > availability? > > > > I tried a power cycle on the main node, and the secondary node=20 > > complained about some root failover, which I'll paste here when I=20 > > capture it, then it rebooted itself after a kernel panic. =20 > Also, the=20 > > secondary node doesn't seem to be able to boot from its own=20 > hard drive=20 > > after a PXE time out. > > -- > > Jiann-Ming Su > > "I have to decide between two equally frightening options. > > If I wanted to do that, I'd vote." --Duckman > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide Read honest=20 > & candid=20 > > reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start=20 > reading now. > > http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick > > _______________________________________________ > > Ssic-linux-users mailing list > > Ssi...@li... > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > >=20 >=20 >=20 >=20 > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide Read honest &=20 > candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users >=20 |
From: Roger T. <op...@bl...> - 2005-02-27 19:16:13
|
Hi Stefan, I'm sorry to hear that. In your email it sounds like you expected us to be obligated to make everything work for you without fail and with minimal effort on your part. It also sounds like you are taking OSS for granted like in free beer. I hope you understand that though it appears there are people here who are sharing their beer, nobody here is obligated to give you free beer whatsoever. It is extremely difficult for these people if you don't help them help you by telling them what they need to know. You can try mentioning what you saw in kdb for example. I hope you do improve on this on your next rather unusual cycle. I mean I hope you'll last longer than 3 months. So when you think it is a good time to try again we'll be here if you need anything, and that's for certain. Hopefully things will be a lot better for you next time, and we'll actually get you up and running step by step. As with DRBD-SSI integration we are making tremendous progress with regards to what is currently available in the clustering community. It's not yet production stable, but this is definitely very exciting for some individuals. Before DRBD-SSI, users without the means to acquire HA shared storage had a much harder time deploying HA-CFS. Other comparable OSS solutions were either inconvenient to acquire or involved much added complexity and code path. I'm sure these users are thrilled to have something like DRBD-SSI. You're welcome. > I think it is a good idea to discuss it on the devel-list. I have the same problems. No failover with drbd, syncing seems to work, but no failover is possible ( power off the root node) the second node entering kdb>!! > I try it since 3 month, now I give up and in the moment I try another solution. > When drbd is working with opennssi I surly come back. > > So long... > > stefan > > >> In general you need both DRBD nodes in a Consistent state >> before doing failover. See /proc/drbd. Usually the first >> time you want to sync the entire root filesystem by issuing a >> --invalidate-remote on the node that has the good data. >> WARNING: If you issue the command on the wrong node you can >> destroy your entire root filesystem with no chance of recovery. Also testing that you can boot cleanly from the failover DRBD >> node is a good idea, before you begin any failover tests. >> One more thing DRBD-SSI code base is not as mature as SSI >> itself. That is why we supply this as an optional package >> separate from the main SSI release. Which DRBD-SSI patch are >> you using? Are you using the drbd-ssi-1.2.0.i686.tar.gz >> package? And which GNU/Linux distro are you using again? >> I think at this stage as we get more technical on this >> DRBD-SSI topic, we can consider continuing this discussion on >> the SSI-devel list. >> Thanks. >> -Roger >> > Now that I've got drbd running with openssi, what are some >> reasonable >> > failure tests to try to verify that this actually provides high availability? >> > >> > I tried a power cycle on the main node, and the secondary node complained about some root failover, which I'll paste here when I capture it, then it rebooted itself after a kernel panic. >> Also, the >> > secondary node doesn't seem to be able to boot from its own >> hard drive >> > after a PXE time out. >> > -- >> > Jiann-Ming Su >> > "I have to decide between two equally frightening options. >> > If I wanted to do that, I'd vote." --Duckman >> > >> > >> > ------------------------------------------------------- >> > SF email is sponsored by - The IT Product Guide Read honest >> & candid >> > reviews on hundreds of IT Products from real users. >> > Discover which products truly live up to the hype. Start >> reading now. >> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> > _______________________________________________ >> > Ssic-linux-users mailing list >> > Ssi...@li... >> > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users >> > >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide Read honest & >> candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Ssic-linux-users mailing list >> Ssi...@li... >> https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > |