Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi all, I have a physical server that I'm setting up as a SAN, the second node won't be available to put online for at least a week. (migrating FROM it to the NEW SAN setup) How do I tell DRBD to I guess stop trying to synchronise? I get pages and pages of [28609.791929] block drbd1: al_complete_io() called on inactive extent 623 [28609.797320] block drbd1: al_complete_io() called on inactive extent 623 [28609.801638] block drbd1: al_complete_io() called on inactive extent 623 [28609.807021] block drbd1: al_complete_io() called on inactive extent 623 [28609.811691] block drbd1: al_complete_io() called on inactive extent 623 [28609.816680] block drbd1: al_complete_io() called on inactive extent 623 [28609.821531] block drbd1: al_complete_io() called on inactive extent 623 [28609.826190] block drbd1: al_complete_io() called on inactive extent 623 [28609.829968] block drbd1: al_complete_io() called on inactive extent 623 [28609.833730] block drbd1: al_complete_io() called on inactive extent 623 [28609.837759] block drbd1: al_complete_io() called on inactive extent 623 I'm running version: 8.3.8.1 (api:88/proto:86-94) So in short I'm wanting to put my primary node online, migrate a bunch of data from a "current" SAN (it's NOT running DRBD, around 7TB of data) to the primary, format rebuild the current THEN sync. Regards, Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20100714/c672c106/attachment.htm>