Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Sandra, Lars,
I have the same problem too:
May 6 09:24:49 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_free_blocks: Freeing blocks in system zones - Block = 152, count = 1
May 6 09:24:49 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_free_blocks: Freeing blocks in system zones - Block = 66037, count = 1
May 6 09:24:49 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_free_blocks: Freeing blocks in system zones - Block = 131573, count = 1
May 6 09:24:49 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_free_blocks: Freeing blocks in system zones - Block = 501, count = 1
May 6 09:37:49 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_new_block: Allocating block in system zone - block = 152
May 6 09:37:49 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_new_block: Allocating block in system zone - block = 501
May 6 09:37:49 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_new_block: Allocating block in system zone - block = 66037
May 6 09:37:49 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_new_block: Allocating block in system zone - block = 131573
May 6 09:52:47 server kernel: EXT3-fs error (device drbd(43,0)):
ext3_check_descriptors: Block bitmap for group 896 not in group (block
29261657)!
but my configuration is very different!
I have master machine with 760Gb on RAID 1+0 by 3Ware controller, It's
LAN-mirrored with drbd version: 0.6.13 (api:64/proto:62) on slave machine
with 777Gb /dev/md0 on software-RAID 0.
I read Lars's suggest about hardware write cache on 3Ware controller and I
turn it off.
I have resolved this problem, so in my log file it does'nt compare more!
Bye, Alessandro