Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Philipp,
Double checked and I haven't been using the amended module, my mistake, I
have
now sorted this out and have recreated the primary side (mke2fs / create
file system).
Once I reconnect the secondary side I can see the following in /proc/drbd
(on secondary node)
version: 0.7.3 (api:75/proto:74)
SVN Revision: 1517:1518 build by root at uklnx03, 2004-09-01 08:37:06
0: cs:SyncTarget st:Secondary/Primary ld:Inconsistent
ns:0 nr:1828 dw:1828 dr:0 al:0 bm:128 lo:0 pe:1 ua:0 ap:0
[>...................] sync'ed: 0.2% (3472860/3472860)K
finish: 12:03:30 speed: 0 (0) K/sec
and after 10 mins it still looks like
version: 0.7.3 (api:75/proto:74)
SVN Revision: 1517:1518 build by root at uklnx03, 2004-09-01 08:37:06
0: cs:SyncTarget st:Secondary/Primary ld:Inconsistent
ns:0 nr:2276 dw:2276 dr:0 al:0 bm:128 lo:0 pe:0 ua:0 ap:0
[>...................] sync'ed: 0.2% (3472448/3472648)K
finish: 72:20:33 speed: 0 (0) K/sec
On the primary node I can see :-
version: 0.7.3 (api:75/proto:74)
SVN Revision: 1517:1518 build by root at uklnx04, 2004-09-01 13:22:35
0: cs:SyncSource st:Primary/Secondary ld:Consistent
ns:2436 nr:0 dw:1088 dr:81241 al:0 bm:0 lo:0 pe:0 ua:0 ap:0
[>...................] sync'ed: 0.2% (3472436/3472648)K
finish: 135:02:21 speed: 0 (0) K/sec
It looks like a forced full sync has been requested but the sync appears
to be hung !
Secondary messages file shows
Sep 1 13:41:40 uklnx03 kernel: drbd0: I am(S):
0:0000000a:00000001:00000045:00000005:01
Sep 1 13:41:40 uklnx03 kernel: drbd0: Peer(P):
1:0000000a:00000001:00000046:00000005:10
Sep 1 13:41:40 uklnx03 kernel: drbd0: drbd0_receiver [1179]: cstate
WFReportParams --> WFBitMapT
Sep 1 13:41:40 uklnx03 kernel: drbd0: Secondary/Unknown -->
Secondary/Primary
Sep 1 13:41:40 uklnx03 kernel: drbd0: drbd0_receiver [1179]: cstate
WFBitMapT --> SyncTarget
Sep 1 13:41:40 uklnx03 kernel: drbd0: Resync started as SyncTarget (need
to sync 3472648 KB [868162 bits set]).
Primary shows
Sep 1 13:41:39 uklnx04 kernel: drbd0: Connection established.
Sep 1 13:41:39 uklnx04 kernel: drbd0: I am(P):
1:0000000a:00000001:00000046:00000005:10
Sep 1 13:41:39 uklnx04 kernel: drbd0: Peer(S):
0:0000000a:00000001:00000045:00000005:01
Sep 1 13:41:39 uklnx04 kernel: drbd0: drbd0_receiver [20316]: cstate
WFReportParams --> WFBitMapS
Sep 1 13:41:40 uklnx04 kernel: drbd0: Primary/Unknown -->
Primary/Secondary
Sep 1 13:41:40 uklnx04 kernel: drbd0: drbd0_receiver [20316]: cstate
WFBitMapS --> SyncSource
Sep 1 13:41:40 uklnx04 kernel: drbd0: Resync started as SyncSource (need
to sync 3472648 KB [868162 bits set]).
Regards
Kevin Izzet
Database / Unix Administrator
Tel: (Code)+44(0)1475 655606
Fax: (Code)+44(0)1475 637755
Email: Kevin.Izzet at nsc.com
"Philipp Reisner" <philipp.reisner at linbit.com>
Sent by: drbd-user-bounces at lists.linbit.com
01/09/2004 13:07
To: drbd-user at lists.linbit.com
cc:
Subject: Re: [DRBD-user] File data corrupt when I switch Nodes
On Wednesday 01 September 2004 12:44, Kevin Izzet wrote:
> Hi Lars,
>
> Changed code and restarted drbd, forced a resync of the secondary
server,
> once
> completed I failed over onto the secondary server and the results are
the
> same.
>
> Failed back to original primary and all ok, ran an fsck.ext3 on both
sides
> (while device primary on each)
> which showed no errors.
>
> Re-created the ext3 file system (mke2fs -j -L drbd0 -b 4096 /dev/drbd0)
> and re-created the file structure,
> tried a switch but the data is still corrupt......
>
And you are 100% sure that you have not used the module with the
sendpage()
call by mistake ?
-philipp
--
: Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :
_______________________________________________
drbd-user mailing list
drbd-user at lists.linbit.com
http://lists.linbit.com/mailman/listinfo/drbd-user
*************************************************************************************
This email may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is prohibited. If you are not the intended or authorised
recipient please contact the sender by reply email and delete all copies
of this message
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20040901/29ced8c1/attachment.htm>