<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">lsblk doesn't only show partitions, but other info as well.<div class="">e.g.</div><div class=""><div class="">sdd 8:48 0 477G 0 disk</div><div class="">└─zbackup_crypt 253:4 0 477G 0 crypt</div><div class=""><br class=""></div><div class="">that is not a partition, it just shows what the device is used for</div><div class="">it will be the same in your case.</div><div class=""><br class=""></div><div class="">Jan</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On 27 Mar 2017, at 15:05, Marco Marino <<a href="mailto:marino.mrc@gmail.com" class="">marino.mrc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">Hi Robert,<br class="">I think the problem is related to the fact that there is a (LVM) partition on top of the drbd device. I tried different configurations and if I use a raw device for the drbd resource and then I use the drbd device without partitions as a PV the problem disappear. Anyway, I dont know if this is really a problem because there is not overlap at all. I (double) checked this using fdisk on /dev/sde and on /dev/drbd2. Both show me a partition that starts at sector 2048. The only problem is that when I use lsblk I see that inside /dev/sde there are 2 devices: /dev/sde1 and /dev/drbd2. I'd like to know if this can cause some kind of problem with performance or data corruption....<br class="">Probably the question is: can I use a raw device as PV? As suggested <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Logical_Volume_Manager_Administration/LVM_components.html#multiple_partitions" class="">here</a> it is possible but there is some problem with the management if I need to enlarge the volume but I don't need this.<br class=""></div><br class=""></div>Marco<br class=""><div class=""><br class=""><div class=""><div class=""><div class=""><br class=""> <br class=""></div></div></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">2017-03-27 9:54 GMT+02:00 Robert Altnoeder <span dir="ltr" class=""><<a href="mailto:robert.altnoeder@linbit.com" target="_blank" class="">robert.altnoeder@linbit.com</a>></span>:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The system looks for partition information at a certain offset on a<br class="">
storage device. If DRBD is used to write directly to a raw storage<br class="">
device, the effect of partitioning the DRBD device on the backing device<br class="">
is the same as if the backing device had been partitioned directly with<br class="">
no DRBD involved.<br class="">
Therefore, the system will see the partition information on the backing<br class="">
device.<br class="">
<br class="">
DRBD internal meta data is written to the end of the backing device<br class="">
(without using any partitioning). The space occupied by the internal<br class="">
meta data will be missing from the DRBD device's size (the DRBD device's<br class="">
size will be the backing device's size minus the space reserved for<br class="">
internal meta data).<br class="">
<div class=""><div class="h5"><br class="">
On 03/25/2017 02:57 PM, Yannis Milios wrote:<br class="">
><br class="">
> Not 100% sure but the first 'partition' could be where drbd stores<br class="">
> metadata?<br class="">
><br class="">
> Your setup should be fine as long ad you can deal in an easy manner<br class="">
> with future resizing of the backing device (sde).<br class="">
><br class="">
> Yannis<br class="">
><br class="">
> root@iscsi2 ~]# lsblk<br class="">
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT<br class="">
> ........<br class="">
> sde 8:64 0 3,7T 0 disk<br class="">
> ├─sde1 8:65 0 3,7T 0 part<br class="">
> └─drbd2 147:2 0 3,7T 0 disk<br class="">
> --<br class="">
> Sent from Gmail Mobile<br class="">
><br class="">
</div></div>br,<br class="">
--<br class="">
Robert Altnoeder<br class="">
<a href="tel:%2B43%201%20817%2082%2092%200" value="+43181782920" class="">+43 1 817 82 92 0</a><br class="">
<a href="mailto:robert.altnoeder@linbit.com" class="">robert.altnoeder@linbit.com</a><br class="">
<br class="">
LINBIT | Keeping The Digital World Running<br class="">
DRBD - Corosync - Pacemaker<br class="">
f / t / in / g+<br class="">
<br class="">
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.<br class="">
______________________________<wbr class="">_________________<br class="">
drbd-user mailing list<br class="">
<a href="mailto:drbd-user@lists.linbit.com" class="">drbd-user@lists.linbit.com</a><br class="">
<a href="http://lists.linbit.com/mailman/listinfo/drbd-user" rel="noreferrer" target="_blank" class="">http://lists.linbit.com/<wbr class="">mailman/listinfo/drbd-user</a><br class="">
</blockquote></div><br class=""></div>
_______________________________________________<br class="">drbd-user mailing list<br class=""><a href="mailto:drbd-user@lists.linbit.com" class="">drbd-user@lists.linbit.com</a><br class="">http://lists.linbit.com/mailman/listinfo/drbd-user<br class=""></div></blockquote></div><br class=""></div></body></html>