Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello Linbit, Do you have a cronjob setup to send an email like that every now and then to prevent us from doing Bad Things (tm)? ;-) @OP: Sorry, couldn't resist. Please see the (Very)FAQ for details, but my "guess" is, you do not use external metadata, so sda3 != drbd0 but sda3 = drbd0 + metadata and you created the filesystem on sda3, not drbd0. I have to "guess" because you did not provide /etc/drbd.conf :-( HTH Joachim Am Donnerstag, 12. Juli 2007 11:32 schrieb Bastian.Marmetschke at nethinks.com: > Hi, > > i am running drbd with heartbeat - actually it worked fine for like 30 > days. Yesterday suddenly following error happend: > > attempt to access beyond end of device > drbd1: rw=0, want=9699344, limit=9505312 > EXT3-fs error (device drbd1): read_inode_bitmap: Cannot read inode bitmap > - block_group = 37, inode_bitmap = 1212417 > Aborting journal on device drbd1. > EXT3-fs error (device drbd1) in ext3_new_inode: IO failure > EXT3-fs error (device drbd1) in ext3_create: IO failure > ext3_abort called. > EXT3-fs error (device drbd1): ext3_journal_start_sb: Detected aborted > journal > Remounting filesystem read-only > > Problem is, that my Partition is now read only. I allready used to stop > drbd / umount the devices and remounted it again. After 1-2 hours I had > the same Problem again. When I used to mount the device, following error > showed up: > > EXT3-fs warning (device drbd2): ext3_clear_journal_err: Filesystem error > recorded from previous mount: IO failure > EXT3-fs warning (device drbd2): ext3_clear_journal_err: Marking fs in need > of filesystem check. > EXT3-fs warning: mounting fs with errors, running e2fsck is recommended > EXT3 FS on drbd2, internal journal > EXT3-fs: recovery complete. > EXT3-fs: mounted filesystem with ordered data mode. > > What might be wrong? I mean it worked before without any problems ? > > cat /proc/drbd > ---------------------- > version: 0.7.21 (api:79/proto:74) > SVN Revision: 2326 build by root at nt3000-slave, 2007-04-23 15:37:50 > 0: cs:Connected st:Primary/Secondary ld:Consistent > ns:1822716 nr:119012 dw:1941728 dr:24833 al:4 bm:12 lo:0 pe:0 ua:0 > ap:0 > 1: cs:Connected st:Primary/Secondary ld:Consistent > ns:3764052 nr:236124 dw:4006376 dr:53970 al:269 bm:30 lo:0 pe:0 ua:0 > ap:0 > 2: cs:Connected st:Primary/Secondary ld:Consistent > ns:5539816 nr:724 dw:5540540 dr:83139 al:191 bm:3 lo:0 pe:0 ua:0 ap:0 > > df output: > ------------- > /dev/drbd0 1921188 66768 1756828 4% /etc/asterisk > /dev/drbd1 4806904 378400 4184320 9% > /var/spool/asterisk > /dev/drbd2 3842376 345356 3301832 10% /var/log/asterisk > > fdisk output: > ------------------ > drbd0 = sda3 > Disk /dev/sda3: 1998 MB, 1998743040 bytes > 255 heads, 63 sectors/track, 243 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Disk /dev/sda3 doesn't contain a valid partition table > > drbd1 = sda5 > Disk /dev/sda5: 5000 MB, 5000937984 bytes > 255 heads, 63 sectors/track, 607 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Disk /dev/sda5 doesn't contain a valid partition table > > drbd2 = sda6 > Disk /dev/sda6: 3997 MB, 3997453824 bytes > 255 heads, 63 sectors/track, 485 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Disk /dev/sda6 doesn't contain a valid partition table > > Thanks advance! > > Bastian Marmetschke > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user