drbdadm create-md fails with “Operation refused.” – what can I do?
the actual error message looks like Found $some filesystem which uses $somuch kB current configuration leaves usable $less kB Device size would be truncated, which would corrupt data and result in ‘access beyond end of device’ errors. You need to either * use external meta data (recommended) * shrink that filesystem first * zero out the device (destroy the filesystem) Operation refused.which means • you created your filesystem before you created your DRBD resource, or • you created your filesystem on your backing device, rather than your DRBD, neither of which is a problem by itself, except – as the error message tries to hint – you need to enlarge the device (e.g. lvextend), shrink the filesystem (e.g. resize2fs), or place the DRBD metadata somewhere else (external meta data). DRBD tries to detect an existing use of the block device in question. E.g. if it detects an existing file system that uses all the available space (as is default for most filesystems), and you try to use DRBD wi
