Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

I get “access beyond end of device” errors, drbd is broken!?

Broken drbd errors
0
Posted

I get “access beyond end of device” errors, drbd is broken!?

0

Your kernel log fills with attempt to access beyond end of device drbd0: rw=1, want=211992584, limit=211986944 Buffer I/O error on device drbd0, logical block 26499072Your file system then remounts read-only, panics or similar. When you try to fsck, you get something like The filesystem size (according to the superblock) is … blocks. The physical size of the device is …+x blocks.Envision this: |– usable area with drbd and internal meta data –|-IMD-| |– real device —————————————–|IMD is “internal meta data”. Once created, it is fixed size. With drbd 0.7 it was fixed 128MB. With drbd 8.0 it is approximately [total storage of real device]/4/8/512/2 rounded up, +36k, rounded up to the next 4k. exaple: grep -e hda4 -e drbd0 /proc/partitions 3 4 105996744 hda4 147 0 105993472 drbd0 ceil(105996744 kB / 32768) == 3235 kB + 36 kB == 3271 kB 4k aligned == 3272 kB 105996744 kB – 3272 kB == 105993472 kBIf you did mkfs /real/device, then later mount through DRBD, t

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123