Re: raidreconf: Successful RAID5 Reconstruction (re-size)

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

 



On Wed, Jun 26, 2002 at 11:35:06AM -0600, Cal Webster wrote:
> 
..
> Although there were no indications of errors and initial indications were
> promising, deeper investigation revealed that the data (or at least the
> directories) have been corrupted.

Did you fsck -f the array before re-sizing the filesystem ?

What does fsck -f show on (the unmounted) filesystem now ?

> 
> When attempting to re-mount iso images located on the RAID device, I got
> "Not a directory" errors.
> 
> A listing at the top level of the mounted RAID5 device shows a somewhat
> garbled directory:
> 
> [root@winggear archive]# df -k
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/hda5              1008952    149796    807904  16% /
> /dev/hda2             25134948  11767212  12090936  50% /home
> /dev/hda1             25134948   2299120  21559028  10% /usr
> /dev/hda4             25136164  18782060   5077244  79% /var
> /dev/md0              69616104  37240476  28839296  57% /usr/local/archive
> 
> [root@winggear root]# cd /usr/local/archive/
> 
> [root@winggear archive]# ls -l
> total 16
> ?-wSrwxr-T  38216 843638119 136403541 3092718354 May 21  1957 backup
> sr-x--S--t  62581 1917696496 1424539385 3344111388 Nov 13  1975 iso
> drwxr-xr-x    2 root     root        16384 Apr 26  2001 lost+found
> b--Sr-xrw-  24320 1593859840 1902061873  44,  49 Jul  8  2002 shares
> 
> There should be four normal directory entries here.

Ough.  Bad bad.

> 
> Anyone know what could have caused this?

Possibly raidreconf.   I am very suspicious about the spare-disk anomaly
that you saw - it is possible that raidreconf did "the bad thing" with
your array.

It is also possible that you have hardware errors, bad cabling, bad
disk, etc.  Anything suspicious in dmesg ?

It is really important to run fsck -f on arrays after running raidreconf
and before re-sizing the filesystem.  For this reason - tracking of
when/where errors occurred.  Of course, it is a little late for you to
be told this now - sorry.  I should add this note to the raidreconf
output after successful reconfiguration.


I will try to see if I can dig out a SCSI crontroller from the crap-heap
here at work, then I will see if I can reproduce the spare-disk error.

It is entirely possible that that is the reason for the screwup.

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux