Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
/ 2004-04-12 07:16:41 -0500 \ Jesse A Dubin: > Thanks for your replies. I'll try to posts answer shortly. I'm > starting to think, though, that my problem is not DRBD, but my file system > after the reboot, which is confusing DRBD into thinking there's something > new there to sync (right before the reboot they should have been completely > synced, so it shouldn't even need to do this) DRBD knows nothing about your file system, it is a block device, below the file system level. With DRBD 0.6.X, whenever a Primary goes down, there has to be a full sync. Even if *you* know that nothing, or only "little", was changed, DRBD has no way to know that. It only knows that the primary vanished unexpectedly, and concludes it needs to sync... > ....I think this would explain > why my data is missing and my server is down.... I still don't understand what you mean with "my data is missing"... Please give more detail about what you are doing, and what you expect to happen, and where "real world" does not meet your expectations. > How destructive will it be if I kill the resync? Not destructive at all... Only next time the nodes connect, the full sync will start over from the very beginning. Lars Ellenberg