Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello,
On 11/28/2011 11:05 AM, Michael Schumacher wrote:
> Hi,
>
> I am running a CENTOS6 server that is temporarily stand alone. I
> succeeded installing drbd on this stand alone machine and I am
> planning to add a secondary machine soon to run drbd in a useful
> primary/secondary configuration.
> However, it was necessary to get the first machine up and running.
> This weekend, I had to reboot the machine and are facing now problems
> to get it up and running again.
>
> This is what /prod/drbd is saying:
>
> ---8<---
> version: 8.4.0 (api:1/proto:86-100)
> GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by dag at Build64R6, 2011-08-12 09:40:17
> 0: cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown C r-----
> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
> 1: cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown C r-----
> ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
> ---8<---
Please use 8.4.0 only for testing, it has som stability issues ... wait
for 8.4.1 if you plan to use it for producive systems.
>
> this is what /var/log/messages is saying:
>
> ---8<---
> Nov 28 09:53:52 virthost1 kernel: drbd: initialized. Version: 8.4.0 (api:1/proto:86-100)
> Nov 28 09:53:52 virthost1 kernel: drbd: GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by dag at Build64R6, 2011-08-12 09:40:17
> Nov 28 09:53:52 virthost1 kernel: drbd: registered as block device major 147
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_data_drbd: Starting worker thread (from drbdsetup [2303])
> Nov 28 09:53:52 virthost1 kernel: block drbd1: open("/dev/sda6") failed with -16
> Nov 28 09:53:52 virthost1 kernel: block drbd1: drbd_bm_resize called with capacity == 0
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_data_drbd: Terminating worker thread
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_root_drbd: Starting worker thread (from drbdsetup [2309])
> Nov 28 09:53:52 virthost1 kernel: block drbd0: open("/dev/sda4") failed with -16
> Nov 28 09:53:52 virthost1 kernel: block drbd0: drbd_bm_resize called with capacity == 0
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_root_drbd: Terminating worker thread
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_data_drbd: Starting worker thread (from drbdsetup [2312])
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_data_drbd: conn( StandAlone -> Unconnected )
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_data_drbd: Starting receiver thread (from drbd_w_fileserv [2313])
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_data_drbd: receiver (re)started
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_data_drbd: conn( Unconnected -> WFConnection )
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_root_drbd: Starting worker thread (from drbdsetup [2315])
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_root_drbd: conn( StandAlone -> Unconnected )
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_root_drbd: Starting receiver thread (from drbd_w_fileserv [2316])
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_root_drbd: receiver (re)started
> Nov 28 09:53:52 virthost1 kernel: d-con fileserver1_root_drbd: conn( Unconnected -> WFConnection )
> Nov 28 09:54:02 virthost1 kernel: block drbd1: State change failed: Need access to UpToDate data
> Nov 28 09:54:02 virthost1 kernel: block drbd1: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:02 virthost1 kernel: block drbd1: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:03 virthost1 kernel: block drbd1: State change failed: Need access to UpToDate data
> Nov 28 09:54:03 virthost1 kernel: block drbd1: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:03 virthost1 kernel: block drbd1: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:04 virthost1 kernel: block drbd1: State change failed: Need access to UpToDate data
> Nov 28 09:54:04 virthost1 kernel: block drbd1: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:04 virthost1 kernel: block drbd1: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:05 virthost1 kernel: block drbd1: State change failed: Need access to UpToDate data
> Nov 28 09:54:05 virthost1 kernel: block drbd1: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:05 virthost1 kernel: block drbd1: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:06 virthost1 kernel: block drbd1: State change failed: Need access to UpToDate data
> Nov 28 09:54:06 virthost1 kernel: block drbd1: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:06 virthost1 kernel: block drbd1: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:07 virthost1 kernel: block drbd0: State change failed: Need access to UpToDate data
> Nov 28 09:54:07 virthost1 kernel: block drbd0: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:07 virthost1 kernel: block drbd0: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:08 virthost1 kernel: block drbd0: State change failed: Need access to UpToDate data
> Nov 28 09:54:08 virthost1 kernel: block drbd0: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:08 virthost1 kernel: block drbd0: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:09 virthost1 kernel: block drbd0: State change failed: Need access to UpToDate data
> Nov 28 09:54:09 virthost1 kernel: block drbd0: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:09 virthost1 kernel: block drbd0: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:10 virthost1 kernel: block drbd0: State change failed: Need access to UpToDate data
> Nov 28 09:54:10 virthost1 kernel: block drbd0: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:10 virthost1 kernel: block drbd0: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:11 virthost1 kernel: block drbd0: State change failed: Need access to UpToDate data
> Nov 28 09:54:11 virthost1 kernel: block drbd0: state = { cs:WFConnection ro:Secondary/Unknown ds:Diskless/DUnknown r----- }
> Nov 28 09:54:11 virthost1 kernel: block drbd0: wanted = { cs:WFConnection ro:Primary/Unknown ds:Diskless/DUnknown r----- }
> ---8<---
>
> I understand that drbd believes that my local data are not up to date.
> However, as there is no secondary machine, there cannot be a
> split-brain situation.
>
> I am wondering how I can convince drbd to connect my local disk again.
Any change PV signatures on these disk were detected and therefore the
VGs where activated automatically? If yes, please adjust your lvm.conf
to ignore it. Don't forget to recreate your initrd/initramfs to also
update it in there.
Regards,
Andreas
--
Need help with DRBD?
http://www.hastexo.com/now
>
> here is my /etc/drbd.d/global_common.conf
> ---8<---
> global {
> usage-count yes;
> }
> common
> {
> handlers {
> #pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-incon-degr.sh; /usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ; reboot -f";
> #pri-lost-after-sb "/usr/lib/drbd/notify-pri-lost-after-sb.sh; /usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ; reboot -f";
> #local-io-error "/usr/lib/drbd/notify-io-error.sh; /usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-trigger ; halt -f";
> }
> startup {
> wfc-timeout 10;
> degr-wfc-timeout 10;
> }
> options {
> }
> disk {
> disk-flushes no;
> disk-barrier no;
> md-flushes no;
> on-io-error pass_on;
> }
> net {
> protocol C;
> }
> }
> ---8<---
>
>
> and this is one of my resource files
>
> ---8<---
> resource fileserver1_data_drbd
>
> {
> startup {
> become-primary-on virthost1;
> }
> on virthost1 {
> device /dev/drbd1;
> disk /dev/sda6;
> address 10.1.1.32:7790;
> meta-disk internal;
> }
> on virthost2 {
> device /dev/drbd1;
> disk /dev/sda6;
> address 10.1.1.33:7790;
> meta-disk internal;
> }
> }
> ---8<---
>
>
> any hints are HIGHLY appreciated.
>
>
> best regards
> ---
> Michael Schumacher
> PAMAS Partikelmess- und Analysesysteme GmbH
> Dieselstr.10, D-71277 Rutesheim
> Tel +49-7152-99630
> Fax +49-7152-996333
> Geschäftsführer: Gerhard Schreck
> Handelsregister B Stuttgart HRB 252024
>
> _______________________________________________
> drbd-user mailing list
> drbd-user at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/drbd-user
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 286 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20111128/561e34be/attachment.pgp>