Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello everyone again, I just added verify-alfg crc32c; to my drbd.conf and ran drbdadm verify all After that I saw lots of out-of-sync secrots in dmesg. I thought: OK, lets sync and then everything should be alright. But after the sync (drbdadm disconnect and connect all on primary one), a re-run of drbdadm verify all still found out-of-sync sectors. So I googled around and saw that there where also people having this problem before. I found the following command and executed this on a sector, reported as out of sync: drbd3: Out of sync: start=192896, size=24 (sectors) <lots of lines of them> [root at saprouter1 ~]# dd if=/dev/sda9 skip=192896 bs=512 count=24 iflag=direct | openssl md5 24+0 records in 24+0 records out 12288 bytes (12 kB) copied, 6.06248 seconds, 2.0 kB/s 6d79f038d772cac9ce34af477574ef7d [root at saprouter2 ~]# dd if=/dev/sda9 skip=192896 bs=512 count=24 iflag=direct | openssl md5 24+0 records in 24+0 records out 12288 bytes (12 kB) copied, 1.93692 seconds, 6.3 kB/s 30704f13388d5e23d644e44996cc2b62 Uh, just found something very strange after executing the command again: [root at saprouter2 ~]# dd if=/dev/sda9 skip=192896 bs=512 count=24 iflag=direct | openssl md5 24+0 records in 24+0 records out 12288 bytes (12 kB) copied, 1.93692 seconds, 6.3 kB/s 30704f13388d5e23d644e44996cc2b62 [root at saprouter2 ~]# dd if=/dev/sda9 skip=192896 bs=512 count=24 iflag=direct | openssl md5 24+0 records in 24+0 records out a2915f04e3533f1f329ac9eab8a875f9 12288 bytes (12 kB) copied, 0.99269 seconds, 12.4 kB/s [root at saprouter2 ~]# dd if=/dev/sda9 skip=192896 bs=512 count=24 iflag=direct | openssl md5 24+0 records in 24+0 records out 12288 bytes (12 kB) copied, 0.856155 seconds, 14.4 kB/s b94b4be0da055b290d4ae4d421cf17f0 [root at saprouter2 ~]# dd if=/dev/sda9 skip=192896 bs=512 count=24 iflag=direct | openssl md5 24+0 records in 24+0 records out 12288 bytes (12 kB) copiedb94b4be0da055b290d4ae4d421cf17f0 , 0.597763 seconds, 20.6 kB/s [root at saprouter2 ~]# dd if=/dev/sda9 skip=192896 bs=512 count=24 iflag=direct | openssl md5 24+0 records in 24+0 records out 12288 bytes (12 kB) copieda2915f04e3533f1f329ac9eab8a875f9 , 0.621022 seconds, 19.8 kB/s [root at saprouter2 ~]# dd if=/dev/sda9 skip=192896 bs=512 count=24 iflag=direct | openssl md5 24+0 records in 24+0 records out 12288 bytes (12 kB) copied6d79f038d772cac9ce34af477574ef7d , 0.041115 seconds, 299 kB/s How could there be sometimes different checksums? O_o Problems with the RAID-driver? Current state is: [root at saprouter1 ~]# /etc/init.d/drbd status drbd driver loaded OK; device status: version: 8.2.6 (api:88/proto:86-88) GIT-hash: 3e69822d3bb4920a8c1bfdf7d647169eba7d2eb4 build by buildsvn at c5-i386-build, 2008-06-02 10:17:29 m:res cs st ds p mounted fstype 0:drbd_afd Connected Secondary/Secondary UpToDate/UpToDate C 1:drbd_ftpdata Connected Secondary/Secondary UpToDate/UpToDate C 2:drbd_saprouter Connected Secondary/Secondary UpToDate/UpToDate C 3:drbd_configs Connected Secondary/Secondary UpToDate/UpToDate C Greetings and sorry for bothering again^^ Florian