[DRBD-user] Question regarding read_inode_bitmap: cannot read inode bitmap -> IO failure

Roberto Nibali ratz at tac.ch
Wed Dec 8 08:40:45 CET 2004

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


Hi Lars,

Thanks for your time. I'm in need of some heavy sleeping. Funny enough it seems 
to come up every once in a while and I was wondering if this (something like my 
corrected 9 point bill) should be put into the FAQ or the installation manual. 
Apologies if it is already present somewhere.

> comparing [B] with [C], ...
> I guess you got the point.

Yes. Sorry for wasting your time. The following indicated that as well:

## /dev/md0
## /dev/drbd0 (wrapped around /dev/md0 with internal meta data)
##

# dumpe2fs -h /dev/md0  | grep ^Blo
dumpe2fs 1.35 (28-Feb-2004)
Block count:              18051008
Block size:               4096
Blocks per group:         32768

(if file system was built on /dev/md0)
# dumpe2fs -h /dev/drbd0  | grep ^Blo
dumpe2fs 1.35 (28-Feb-2004)
Block count:              18051008
Block size:               4096
Blocks per group:         32768

(if file system was built on /dev/drbd0)
# dumpe2fs -h /dev/drbd0  | grep ^Blo
dumpe2fs 1.35 (28-Feb-2004)
Block count:              18018240
Block size:               4096
Blocks per group:         32768

Note: ( 18051008 - 18018240 ) * 4096 = 131072 bytes (128Mb)

Which makes all perfect sense. Thank you and best regards,
Roberto Nibali, ratz
-- 
-------------------------------------------------------------
addr://Rathausgasse 31, CH-5001 Aarau  tel://++41 62 823 9355
http://www.terreactive.com             fax://++41 62 823 9356
-------------------------------------------------------------
terreActive AG                       Wir sichern Ihren Erfolg
-------------------------------------------------------------



More information about the drbd-user mailing list