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

Michael Haverkamp mhaverkamp at kcp.com
Mon Dec 6 16:06: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.


You definitely did "b".  Your steps should look more like this.

1. Configure two scsi disks of 74GB with 1 partition
2. Set label to "Linux Raid Autodectect"
3. Create raidtab
4. mkraid /dev/md0
[... RAID is synching ...]
5. Create drbd.conf with device /dev/drbd0, disk /dev/md0 and
meta-disk-internal
6. mke2fs -j /dev/drbd0
7. tunefs -c 0 -i 0 /dev/drbd0
8. Repeat 1-7 on second node
9. Invoke /etc/init.d/drbd start

Roberto Nibali wrote:
> Hello,
> 
> Reading [1] on the subject, I learn that two things can cause that:
> 
> a. meta data is on top of en existing filesystem
> b. internal meta data is used but mkfs was done on lower level device
> 
> I'd like to share what I believe was our setup procedure for the DRBD 
> installation for a HA cluster:
> 
> 1. Configure two scsi disks of 74GB with 1 partition
> 2. Set label to "Linux Raid Autodectect"
> 3. Create raidtab
> 4. mkraid /dev/md0
> [... RAID is synching ...]
> 5. mke2fs -j /dev/md0
> 6. tunefs -c 0 -i 0 /dev/md0
> 7. Create drbd.conf with device /dev/drbd0, disk /dev/md0 and 
> meta-disk-internal
> 8. Repeat 1-7 on second node
> 9. Invoke /etc/init.d/drbd start
> 
> Do you see something in this shortened installation guideline that 
> applies to either a or b? If so could you kindly tell me where and how 
> to address this?
> 
> [1] http://marc.free.net.ph/message/20040919.215542.e4c54ac6.html
> 
> Best regards,
> Roberto Nibali, ratz

-- 
Michael Haverkamp



More information about the drbd-user mailing list