[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Software RAID-1 partition overflow



	A code ran wild and filled a software raid-1 partition.  This made the
machine unresponsive (ssh into this partition). After some puzzling, I
pushed the hardware reset.  Upon reboot Linux was unable to mount the
raid  partition.   Grepping through TLDP the fixes all seem to assume you
can mount at least one of the two images. I have manually mounted all the
other partitions and the system seems to work: But since the trashed
partition is /home the present configuration is not useful. When I try to
mount /dev/md0
or /dev/hda7 or /dev/hdb2  I get the generic error message which lists 5
possible problems.

Hopefully someone else has been in this tar pit before me?
                               TIA -  Pat
Would greatly appreciate any help since I have been remiss and have
backed up /home
    since Apr  and the users are not going to be amused.
-------------------------------------------------------------------------
--------
For masochists - here are some of the details
        from  /var/log/messages
Jul  8 00:28:53 fortran-0 kernel: Unexpected dirty buffer encountered at
do_get_write_access:613 (09:00 blocknr 0)

Jul  8 00:28:53 fortran-0 kernel: attempt to access beyond end of device

Jul  8 00:28:53 fortran-0 kernel: 09:00: rw=0, want=951630048,
limit=6530304

Jul  8 00:28:53 fortran-0 kernel: EXT3-fs error (device md(9,0)):
ext3_get_inode_loc: unable to read inode block - inode=294637,
block=774778423
Jul  8 00:28:53 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_reserve_inode_write: IO failure
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_orphan_add: IO failure
Jul  8 00:28:54 fortran-0 kernel: attempt to access beyond end of device
Jul  8 00:28:54 fortran-0 kernel: 09:00: rw=0, want=12632296,
limit=6530304
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)):
ext3_get_inode_loc: unable to read inode block - inode=425468,
block=540028985
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_reserve_inode_write: IO failure
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_orphan_add: IO failure
Jul  8 00:28:54 fortran-0 kernel: attempt to access beyond end of device
Jul  8 00:28:54 fortran-0 kernel: 09:00: rw=0, want=12632296,
limit=6530304
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)):
ext3_get_inode_loc: unable to read inode block - inode=425468,
block=540028985


Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_reserve_inode_write: IO failure

Jul  8 00:28:54 fortran-0 kernel: attempt to access beyond end of device

Jul  8 00:28:54 fortran-0 kernel: 09:00: rw=0, want=12632296,
limit=6530304

Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)):
ext3_get_inode_loc: unable to read inode block - inode=425468,
block=540028985
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_reserve_inode_write: IO failure
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_orphan_add: IO failure
Jul  8 00:28:54 fortran-0 kernel: attempt to access beyond end of device
Jul  8 00:28:54 fortran-0 kernel: 09:00: rw=0, want=12632296,
limit=6530304
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)):
ext3_get_inode_loc: unable to read inode block - inode=425468,
block=540028985
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_reserve_inode_write: IO failure
Jul  8 00:28:54 fortran-0 kernel: EXT3-fs error (device md(9,0)) in
ext3_setattr: IO failure
Jul  8 00:28:54 fortran-0 kernel: attempt to access beyond end of device
Jul  8 00:28:54 fortran-0 kernel: 09:00: rw=0, want=951630048,
limit=6530304
Jul  8 00:28:54 fortran-0 kernel: EXT
=============================
	This repeats for ~130k lines (8 minutes) then an additional line
  is added to the cycle
Freeing block not in detezone block=105291 count =1

	This combination repeats for ~140k lines (5 minutes) and
then  there is 
	signal 15 (presumably the forced shutdown)
========================

lsread gives
lsread
[dev 3, 7] /dev/hda7:
	md version		= 0.90.0
	superblock uuid		= FD44C069.4C5A1EA2.26992AA5.9E3085B7
	md minor number		= 0
	created			= 1040323422 (Thu Dec 19 13:43:42 2002)
	last updated		= 1057704393 (Tue Jul  8 18:46:33 2003)
	raid level		= 1
	chunk size		= 64 KB
	apparent disk size	= 6530304 KB
	disks in array		= 2
	required disks		= 2
	active disks		= 2
	working disks		= 2
	failed disks		= 0
	spare disks		= 0
	position in disk list	= 0
	position in md device	= 0
	state			= good

[dev 3, 66] /dev/hdb2:
	md version		= 0.90.0
	superblock uuid		= FD44C069.4C5A1EA2.26992AA5.9E3085B7
	md minor number		= 0
	created			= 1040323422 (Thu Dec 19 13:43:42 2002)
	last updated		= 1057704393 (Tue Jul  8 18:46:33 2003)
	raid level		= 1
	chunk size		= 64 KB
	apparent disk size	= 6530304 KB
	disks in array		= 2
	required disks		= 2
	active disks		= 2
	working disks		= 2
	failed disks		= 0
	spare disks		= 0
	position in disk list	= 1
	position in md device	= 1
	state			= good

===================================================================
   raidtab is
raiddev		    /dev/md0
raid-level		    1
nr-raid-disks		    2
chunk-size		    64k
persistent-superblock	    1
nr-spare-disks		    0
    device	    /dev/hda7
    raid-disk     0
    device	    /dev/hdb2
    raid-disk     1
 =====================================================
	sfdisk -l /dev/hda  gives

Disk /dev/hda: 2482 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start     End   #cyls   #blocks   Id  System
/dev/hda1   *      0+     12      13-   104391   83  Linux
/dev/hda2         13    1032    1020   8193150   83  Linux
/dev/hda3       1033    1414     382   3068415   83  Linux
/dev/hda4       1415    2481    1067   8570677+   f  Win95 Ext'd (LBA
/dev/hda5       1415+   1541     127-  1020096   83  Linux
/dev/hda6       1542+   1668     127-  1020096   82  Linux swap
/dev/hda7       1669+   2481     813-  6530391   fd  Linux raid
autodetect
===========================
 




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]