Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Thank you Roland, I think you are right, also thank you for trying. Etienne On 16/02/2011 16:26, Roland Friedwagner wrote: > IMHO this has nothing to do with drbd. > It is probably a problem with your LVM. > > You may add "r|/dev/dm-.*|" to your lvm filter list. > But this should be equal as your current lvm filter > filter = [ "a|drbd.*|", "a|md.*|", "r|.*|" ] > ignores it already. > > But you get /dev/dm-3 as PV for VG vm and dm-3 is the same > as /dev/system/drbd. > > So clean up you lvm cache (to be sure) > rm /etc/lvm/cache/.cache > > Do vgscan -vvv (3vvv!) and you can also see how the regexes of you > filter gets applied. > > And final check your distros lvm.conf in initrd. > You may to have to recreate initrd if you change the lvm filter. > And keep a backup boot entry, because you may miss your root fs on > reboot when it does exclude your system VG. > > Am Mittwoch 16 Februar 2011 schrieb Etienne Pretorius: >> Hello Roland, >> >> I attached the output to this email. >> >> I noticed that DRBD is started at the end of the boot process but LVM >> is obviously started before that. >> That means that I have to rescan for volume groups after DRBD has >> started, but it still does not explain why I can not use the device >> after the reboot. >> >> I have made the changes to drdb.res as you have requested. >> >> Thank you. >> Etienne Pretorius > >