Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Todd Denniston wrote:
> What about a slight modification to your procedure
> Lars get your clue stick, I bet you'll need to beat me with it :)
>
> Andreas Semt wrote:
>
> <SNIP>
>
>>Okay, now I have two possible ways to go, but can I suggest a third way
>>(cause I won't use LVM2, so only one way left ...)?
>>
>>The situation is:
>>
>>nodeA (Heartbeat and drbd active), nodeB (Heartbeat and drbd standby).
>>To make a clean and consistent snapshot i will do following (all on nodeB!):
>
> a0) on Node A at 01:59 per cron { while [ time != 0201 ]; do sync;done }
>
>>a) stop heartbeat (at 02.00 pm per cron for example), i.e. that means
>> for heartbeat: "nodeB is dead!, i am the only one left!"
>>b) -> <not right>
>>c) shut down drbd (or heartbeat shut down drbd)
>
> Now drbd knows nothing about the other node.
> c1) violate a drbd tenet:
> mount -t ext2 -o ro /dev/device_under_drbd /mnt_point
No, i won't do this! Not after the discussion with Lars. Not anymore!
> # perhaps a thinko here, you do not want the
> #journal ran because that would change the under device
> #with out drbd knowing. (assumption ext3 filesystem)
See the "Do and Don't" from Linux Mag!
http://www.drbd.org/drbd-article.html#limitations__the_do_and_don't
--
Best regards,
Andreas Semt