Re: corrupted resource can't be fixed be rolling back to old snapshot

Chitvan Chhabra <[email protected]>
Newsgroups gmane.comp.linux.drbd
Message-ID <CAF9uJd2Yn4U6YHqoweSLvOnj4AkhmFbJnz+rrb5v_f34=7m85A@mail.gmail.com>
Unable to see the older thread.May Be it is just me.Request to share older
conversation as well please.

Thanks and Regards,
Chitvan Chhabra

On Tue, 2 Aug 2022 at 14:34, Joel Colledge <[email protected]> wrote:

> Hi Michael,
>
> Are you using the most recent version of drbd-utils? There have been a
> few fixes over the years which might be related.
>
> Perhaps the hardware problems affected the metadata long ago and now
> the corrupted metadata is present in all the snapshots.
>
> If that is not the case, this looks to me more like a bug than a
> misunderstanding of how DRBD works. Are you able to reproduce the
> issue starting from a fresh volume? It could be that this particular
> combination of device size and bitmap slot count triggers a bug that
> no-one else has yet encountered. A reproducer would be necessary to
> work on fixing it.
>
> Best regards,
> Joel
> _______________________________________________
> Star us on GITHUB: https://github.com/LINBIT
> drbd-user mailing list
> [email protected]
> https://lists.linbit.com/mailman/listinfo/drbd-user
>

_______________________________________________
Star us on GITHUB: https://github.com/LINBIT
drbd-user mailing list
[email protected]
https://lists.linbit.com/mailman/listinfo/drbd-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.