On 2010-07-14 07:54, [email protected] wrote: > 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
That information yanked out of context isn't all that helpful. Can you upload a complete (but gzip or bzip2 compressed) to some web space, dropbox, or similar, and post the URL here? Thanks. Cheers, Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
