Ah, I was taking the removed entry as being equivalent to the spare
entry, i.e. the disk had been removed from the array and was being
treated as spare ... but as this was due to an issue it was still
listed as removed too ... that thought appears to be incorrect.
I think, in hindsight, that the removed disk was one from when I first
tried to set this up and one of the disks failed (hardware issue). It
looks like some configuration file was keeping hold of that
information even though the array had been dropped and recreated
several times since then.
Anyway ... i have done the following .... patched the system up to
date, removed the raid configuration and recreated it with the same
results and then rebooted. After the reboot the mdadm and
/proc/mdstat indicated that the system was rebuilding the spare disk.
I left this for a couple of hours and now everything looks as it
should (6 active disks).
Currently partitioning and formatting so hopefully every is ok now and
is as expected.
belgarath:~ # mdadm --detail --scan -vvv
/dev/md0:
Version : 01.00.03
Creation Time : Sun Dec 2 18:15:41 2007
Raid Level : raid5
Array Size : 2441918720 (2328.80 GiB 2500.52 GB)
Used Dev Size : 976767488 (465.76 GiB 500.10 GB)
Raid Devices : 6
Total Devices : 6
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sun Dec 2 21:41:02 2007
State : active
Active Devices : 6
Working Devices : 6
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 128K
Name : 0
UUID : c4c1b89b:2a017fbb:6e59a200
:1d0e2931
Events : 13
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 49 2 active sync /dev/sdd1
3 8 65 3 active sync /dev/sde1
4 8 81 4 active sync /dev/sdf1
6 8 97 5 active sync /dev/sdg1
(sdc is a 160GB disk and is used for the OS which is why its not listed here)
Anyway, all is looking good now so many thanks to all those whose replied.
Cheers
Tim
On Dec 2, 2007 8:04 PM, Carlos E. R. <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
>
> The Sunday 2007-12-02 at 19:38 -0000, Tim Hempstead wrote:
>
> > Noting that that is very rough as a 500GB disk is only ~467GB usable
> > anyway due to the way the manafacturers define disk sizes.
>
> No, a 500GB is really 500 GB. However, that is 465 GiB.
>
> "They" have it right - even if perhaps for the wrong motives :-p
>
> http://en.wikipedia.org/wiki/GiB
>
>
> > Of course I could be wrong here but I normally don't expect to see a
> > disk in the spare state in a normal RAID5 array, (but all the arrays I
> > have seen using Linux Software RAID up to now have had a maximum of 4
> > disks and this has 6)
>
> But you have 7 disk listed:
>
> ] Number Major Minor RaidDevice State
>
> ] 0 8 1 0 active sync /dev/sda1
> ] 1 8 17 1 active sync /dev/sdb1
> ] 2 8 49 2 active sync /dev/sdd1
> ] 3 8 65 3 active sync /dev/sde1
> ] 4 8 81 4 active sync /dev/sdf1
> ] 5 0 0 5 removed
> ]
> ] 6 8 97 - spare /dev/sdg1
>
> You should remove disk number 5 from the definition, that would remove the
> degraded state.
>
> And I don't see sdc1?
>
> - --
> Cheers,
> Carlos E. R.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4-svn0 (GNU/Linux)
>
> iD8DBQFHUw/ktTMYHG2NR9URAtKMAJwIgJXenDN3VrGU2oSCOTu9yStsYwCeIFAF
> tnDpmDn9ZiC6axtx286ZJUA=
> =DdgM
> -----END PGP SIGNATURE-----
> --
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Tim Hempstead
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
