mdadm on lenny64, why two spares?

[whollygoat@letterboxes.org]

Can anyone tell me why the following command 
creates 2 spares instead of just one?

# mdadm -C /dev/md0 -v -e1 -l5 -b internal \
  -n3 /dev/hde1 /dev/hdg1 /dev/hdi1 \
  -x1 /dev/hdk1 --name FileServ -a yes

# mdadm -D /dev/md0
/dev/md0:
        Version : 01.00
  Creation Time : Sat Jun  6 19:34:29 2009
     Raid Level : raid5
     Array Size : 156250880 (149.01 GiB 160.00 GB)
  Used Dev Size : 156250880 (149.01 GiB 160.00 GB)
   Raid Devices : 3
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Sat Jun  6 19:34:29 2009
          State : active, degraded
 Active Devices : 2
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 2

         Layout : left-symmetric
     Chunk Size : 64K

           Name : fly:FileServ  (local to host fly)
           UUID : 9da80d4a:237fae62:77b7ead6:86e9900e
         Events : 0

    Number   Major   Minor   RaidDevice State
       0      33        1        0      active sync   /dev/hde1
       1      34        1        1      active sync   /dev/hdg1
       2       0        0        2      removed

       3      57        1        -      spare   /dev/hdk1
       4      56        1        -      spare   /dev/hdi1

I've tried running it a few times, zeroing the superblock before
each attempt.

Thanks,

will
-- 
  
  whollygoat@letterboxes.org

-- 
http://www.fastmail.fm - Or how I learned to stop worrying and
                          love email again