Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Alan Robertson wrote: > Andrew wrote: > >> Alan Robertson wrote: >> >>> Andrew wrote: >>> >>>> Hi, >>>> >>>> I'm using DRBD version 0.6.12. Having some troubles with EXT3 >>>> reporting "attempt to access beyond end of device". >>>> >>>> I first noticed a problem when i tried to mkdir. : >>>> >>>> [root at jack www]$ mkdir test >>>> mkdir: cannot create directory `test': Input/output error >>>> >>>> I'm getting EXT3 errors in /var/log/messages such as : >>>> >>>> Sep 17 11:15:20 jack kernel: attempt to access beyond end of device >>>> Sep 17 11:15:20 jack kernel: 2b:00: rw=0, want=100270088, >>>> limit=100179416 >>>> Sep 17 11:15:20 jack kernel: EXT3-fs error (device drbd(43,0)): >>>> read_inode_bitmap: Cannot read inode bitmap - block_group = 765, >>>> inode_bitmap = 25067521 >>>> Sep 17 11:15:20 jack kernel: EXT3-fs error (device drbd(43,0)) in >>>> ext3_new_inode: IO failure >>>> >>>> [root at jack nai2]# df -k /data/ >>>> Filesystem 1K-blocks Used Available Use% Mounted on >>>> /dev/nb0 100179416 5002344 90088204 6% /data >>>> >>>> [root at jack nai2]# /sbin/fdisk -s /dev/nb0 >>>> 100179416 >>>> >>>> in drbd.conf: >>>> disk-size = 100179416k >>>> >>>> So i'm just wondering if anyone has any ideas on what might be wrong ? >>> >>> >>> >>> >>> It might be corrupted. >>> >>> When did you last run fsck on it? >>> >>> >> would have been a fair while .... maybe 3-4 months.... should I give >> fsck a go? any particular options I should use with fsck ? > > > Not that I know of. > > If taking this system down is difficult, you could even do an fsck -n > with it mounted. It might produce errors, but if you do it several > times, and each time it gives the same errors, then it's probably > worth unmounting it and checking it out the right way. when i run fsck ... i get : [nai2 at jack nai2]$ sudo /sbin/fsck -n /dev/nb0 fsck 1.34 (25-Jul-2003) e2fsck 1.34 (25-Jul-2003) Warning! /dev/nb0 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. The filesystem size (according to the superblock) is 25444352 blocks The physical size of the device is 25044854 blocks Either the superblock or the partition table is likely to be corrupt! Abort? no /dev/nb0 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Deleted inode 1015829 has zero dtime. Fix? no Error reading block 25067522 (Invalid argument) while doing inode scan. Ignore error? no Error while scanning inodes (12533760): Can't read next inode e2fsck: aborted /dev/nb0: ********** WARNING: Filesystem still has errors ********** /dev/nb0: 6092/12730368 files (1.0% non-contiguous), 1650145/25444352 blocks