Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On 2004-09-23T15:30:09,
Philipp Reisner <philipp.reisner at linbit.com> said:
> * You have to fix the RAM of the secondary machine.
> (In case you really have the issue you reference to)
> Maybe you should post that OOPS ...
>
> The item 5 of drbd-0.8 roadmap will have the effect that the
> primary node will write something like "Got invalid block-id"
> to its Syslog and disconnect.
Yes, but with memory corruption, there's no telling what the secondary
might be writing to disk, or returning for a read. It's good to try and
fortify the primary, but:
> --> You have to fix the RAM of the secondary...
is really the only option.
Of course, I'd fully appreciate it if he sponsored the development of
that feature for 0.7 along with an online-consistency check of the two
mirrors ;-)
Sincerely,
Lars Marowsky-Brée <lmb at suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company