[DRBD-user] umount costs lots of time in drbd 8.4.3

Mia Lueng xiaozunvlg at gmail.com
Wed May 8 18:16:56 CEST 2013

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.


in drbd 8.4.3,I do the following test:

[root at kvm3 drbd.d]# drbdadm dump drbd0
# resource drbd0 on kvm3: not ignored, not stacked
# defined at /etc/drbd.d/drbd0.res:1
resource drbd0 {
    on kvm3 {
        device           /dev/drbd0 minor 0;
        disk             /dev/vg_kvm3/drbd0;
        meta-disk        internal;
        address          ipv4 192.168.10.6:7700;
    }
    on kvm4 {
        device           /dev/drbd0 minor 0;
        disk             /dev/vg_kvm4/drbd0;
        meta-disk        internal;
        address          ipv4 192.168.10.7:7700;
    }
    net {
        protocol           A;
        csums-alg        md5;
        verify-alg       md5;
        ping-timeout      30;
        ping-int          30;
        max-epoch-size   8192;
        max-buffers      8912;
        unplug-watermark 131072;
    }
    disk {
        on-io-error      pass_on;
        disk-barrier      no;
        disk-flushes      no;
        resync-rate      100M;
        c-plan-ahead      20;
        c-delay-target   100;
        c-max-rate       400M;
        c-min-rate        2M;
        al-extents       601;
    }
}

[root at kvm3 oradata]# dd if=t1 of=t2 bs=1M
5585+1 records in
5585+1 records out
5856305152 bytes (5.9 GB) copied, 286.119 s, 20.5 MB/s
[root at kvm3 oradata]# cd
[root at kvm3 ~]# umount /oradata


it takes lots of time(up to 600 seconds)  to umount the drbd mount point.

echo "1" >/proc/sys/vm/block_dump
show when umount ,

[root at kvm3 ~]# dmesg|tail -n 100
flush-253:5(3907): WRITE block 31475520 on dm-5
flush-253:5(3907): WRITE block 31475528 on dm-5
flush-253:5(3907): WRITE block 31475536 on dm-5
flush-253:5(3907): WRITE block 31475544 on dm-5
flush-253:5(3907): WRITE block 31475552 on dm-5
flush-253:5(3907): WRITE block 31475560 on dm-5
flush-253:5(3907): WRITE block 31475568 on dm-5
flush-253:5(3907): WRITE block 31475576 on dm-5
flush-253:5(3907): WRITE block 31475584 on dm-5
flush-253:5(3907): WRITE block 31475592 on dm-5
flush-253:5(3907): WRITE block 31475600 on dm-5
flush-253:5(3907): WRITE block 31475608 on dm-5
flush-253:5(3907): WRITE block 31475616 on dm-5
flush-253:5(3907): WRITE block 31475624 on dm-5
flush-253:5(3907): WRITE block 31475632 on dm-5
flush-253:5(3907): WRITE block 31475640 on dm-5
flush-253:5(3907): WRITE block 31475648 on dm-5
flush-253:5(3907): WRITE block 31475656 on dm-5
flush-253:5(3907): WRITE block 31475664 on dm-5
flush-253:5(3907): WRITE block 31475672 on dm-5
flush-253:5(3907): WRITE block 31475680 on dm-5
flush-253:5(3907): WRITE block 31475688 on dm-5
flush-253:5(3907): WRITE block 31475696 on dm-5
flush-253:5(3907): WRITE block 31475704 on dm-5
flush-253:5(3907): WRITE block 31475712 on dm-5
flush-253:5(3907): WRITE block 31475720 on dm-5
drbd_submit(2898): WRITE block 209715144 on dm-3
jbd2/dm-5-8(3897): WRITE block 100927848 on dm-5
jbd2/dm-5-8(3897): WRITE block 100927856 on dm-5
jbd2/dm-5-8(3897): WRITE block 100927864 on dm-5
jbd2/dm-5-8(3897): WRITE block 100927872 on dm-5
jbd2/dm-5-8(3897): WRITE block 100927880 on dm-5
jbd2/dm-5-8(3897): WRITE block 100927888 on dm-5
jbd2/dm-5-8(3897): WRITE block 100927896 on dm-5
jbd2/dm-5-8(3897): WRITE block 100927904 on dm-5
flush-253:5(3907): WRITE block 12582992 on dm-5
flush-253:5(3907): WRITE block 12583000 on dm-5
flush-253:5(3907): WRITE block 12583008 on dm-5
flush-253:5(3907): WRITE block 12583016 on dm-5
flush-253:5(3907): WRITE block 12583024 on dm-5
umount(3958): WRITE block 8 on dm-5
flush-253:5(3907): WRITE block 12583032 on dm-5
flush-253:5(3907): WRITE block 16777296 on dm-5
flush-253:5(3907): WRITE block 29360160 on dm-5
umount(3958): WRITE block 8456 on dm-5
flush-253:5(3907): WRITE block 29360168 on dm-5
flush-253:5(3907): WRITE block 29360176 on dm-5
umount(3958): WRITE block 5996544 on dm-5
flush-253:5(3907): WRITE block 29360184 on dm-5
flush-253:5(3907): WRITE block 29360192 on dm-5
flush-253:5(3907): WRITE block 12582984 on dm-5
drbd_submit(2898): WRITE block 209715152 on dm-3
drbd_submit(2898): WRITE block 209715160 on dm-3
umount(3958): WRITE block 0 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 100925440 on dm-5
umount(3958): WRITE block 0 on dm-5
umount(3958): dirtied inode 1053911 (mtab.tmp) on dm-0
umount(3958): dirtied inode 1053911 (mtab.tmp) on dm-0
umount(3958): WRITE block 33845632 on dm-0
umount(3958): dirtied inode 1053912 (?) on dm-0


Is the reason that I use protocol A?


Best Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20130509/b1844847/attachment.htm>


More information about the drbd-user mailing list