Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Diskless means just what it sounds like. The disk is not available. Probably it’s been grabbed by the LV manager. A primary/diskless node will simply do I/O on the peer, but I don’t believe that will work unless the peer is also primary – which is not your situation. I don’t think you are looking at what you believe you are looking at. hth Dan From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Edwige Odedele Sent: Thursday, July 21, 2011 7:28 AM To: 'Felix Frank'; 'drbd-user' Subject: Re: [DRBD-user] cs: Unconfigured Hi, I just want you to know that it is working beside the issue of this commands: > root at sd-xxxx5:~# cat /proc/drbd > version: 8.3.7 (api:88/proto:86-91) > GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by root at sd-xxxx5, > 2011- > 05-04 10:47:00 > 0: cs:Connected ro:Secondary/Secondary ds:Diskless/UpToDate C r---- I made the node primary and also test: lvscan, pvscan, vgscan and all issues was right. I also checked the disk contains. But I wonder to know why I still have ds:Diskless. Did somebody ever faced this problem? Best Regards, Edwige ODEDELE -----Message d'origine----- De : Felix Frank [mailto:ff at mpexnet.de] Envoyé : mercredi 20 juillet 2011 12:09 À : Edwige Odedele; drbd-user Objet : Re: [DRBD-user] cs: Unconfigured On 07/20/2011 12:03 PM, Edwige Odedele wrote: > root at sd-xxxx5:~# cat /proc/drbd > version: 8.3.7 (api:88/proto:86-91) > GIT-hash: ea9e28dbff98e331a62bcbcc63a6135808fe2917 build by root at sd-xxxx5, > 2011- > 05-04 10:47:00 > 0: cs:Connected ro:Secondary/Secondary ds:Diskless/UpToDate 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 Please disconnect that. > root at sd-xxxx5:~# lvs > It's not abundantly clear to me what's holding your lower device, so you will need to find that out on your own (lsof and fuser come to mind). I'm especially unsure whether the empty lvs output means that LVM is not the culprit. You may want to check vgscan, pvs and their ilk. Do find out what has claimed your backing device. That's the single most important step right now. HTH, Felix -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110721/5376146a/attachment.htm>