4

I was configuring two DRBD shares for our servers. I have successfully completed two DRBD share creation, but while checking the status one of the shares status is showing as "UpToDate/Diskless".

drbd-overview command output

[root@server1~]#drbd-overview 

  1:drbd   Connected Secondary/Primary UpToDate/UpToDate C r---- 
  2:drbd1  Connected Primary/Secondary   UpToDate/Diskless C r----

[root@server2~]#drbd-overview

  1:drbd   Connected Primary/Secondary UpToDate/UpToDate C r---- 
  2:drbd1  Connected Secondary/Primary   Diskless/UpToDate C r---- 

The DRBD is working correctly and i can mount the devices on primary nodes.

But i am wondering about one DRBD share status. is that status is normal or is there anything wrong with that share ??

Thanks in advance.

4

This is not normal at all (everything else than UpToDate is not normal). Check if the disk you configured in the config file exists and works correctly.

From the docs:

Diskless. No local block device has been assigned to the DRBD driver. This may mean that the resource has never attached to its backing device, that it has been manually detached using drbdadm detach, or that it automatically detached after a lower-level I/O error.

  • Thank you for your reply. I have re-created the DRBD share and now everything works fine. – itzforu Nov 28 '12 at 14:46
1

these commands will help you fix the problem. Run the following commands on the Diskless node.

drbdadm detach
drbdadm connect
drbdadm attach
restart the drbd service <--- this is important step

-2

Both nodes should be UpToDate

Look like you should attach the disk at the diskless side. Go to the secondary node and execute

drbdadm attach drbd1

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.