Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
*********************** This mail has been scanned by InterScan MSS. ***********-*********** Dear Lars, Yes, it will work with smaller device, were up to 2 Terabytes. What else do i need to run replication over 2tb? thanks, francism ----- Original Message ----- From: "Lars Ellenberg" <Lars.Ellenberg at linbit.com> To: <drbd-user at lists.linbit.com> Sent: Tuesday, September 13, 2005 11:40 PM Subject: Re: [DRBD-user] Replication of 3TB goes to stand Alone-workerterminated / 2005-09-13 19:26:39 +0800 \ Francis I. Malolot: > sending you the unfiltered kernel > bufffer log, Okey we assume that is a memory > issue but we increase our memory to 2GB and set vmalloc to 512m > its still the same problem.we also check vmstat it also did not > got low memory. > drbd0: Creating state block > drbd0: resync bitmap: bits=768000000 words=24000000 > drbd0: size = 2929 GB (3072000000 KB) > drbd0: 3072000000 KB now marked out-of-sync by on disk bit-map. > drbd0: Assuming that all blocks are out of sync (aka FullSync) > drbd0: 3072000000 KB now marked out-of-sync by on disk bit-map. > drbd0: drbdsetup [5288]: cstate Unconfigured --> StandAlone > drbd0: drbdsetup [6309]: cstate StandAlone --> Unconnected right here are messages missing. either some sort of "sorr, got no memory for this and that", or "sorry, could not get a socket", or "sorry, peer reset connection, doing this and that"... not exactly in that wording. > drbd0: drbdsetup [6309]: cstate Unconnected --> StandAlone > drbd0: drbdsetup [6309]: cstate StandAlone --> Unconfigured > drbd0: worker terminated currently, I'd say there is something else wrong. those kernel messages log the pid, too. so we know that the last three state changes come from the same drbdsetup, which is the drbdsetup net call. that ioctl does not set StandAlone or Unconfigured. it only starts the worker, makes the state change -> Unconnected, and starts the receiver. other, subsequent state changes would happen in worker or receiver context. the messages above indicate those would happen within the very same drbdsetup context. "this cannot happen" :-( still, just to rule it out: does it work for you with smaller device sizes? if yes, up to which size? -- : Lars Ellenberg Tel +43-1-8178292-0 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schoenbrunner Str. 244, A-1120 Vienna/Europe http://www.linbit.com : __ please use the "List-Reply" function of your email client. _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user