problem with spare, acive device, clean degrated, reshaip RADI5, anybody can help ?

problem with spare, acive device, clean degrated, reshaip RADI5, anybody can help ?

[Andreas-Sokov]

Hello linux-raid.

i have DEBIAN.

raid01:/# mdadm -V
mdadm - v2.6.4 - 19th October 2007

raid01:/# mdadm -D /dev/md1
/dev/md1:
        Version : 00.91.03
  Creation Time : Tue Nov 13 18:42:36 2007
     Raid Level : raid5
     Array Size : 1465159488 (1397.29 GiB 1500.32 GB)
  Used Dev Size : 488386496 (465.76 GiB 500.11 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Sun Jan 27 00:24:44 2008
          State : clean, degraded
 Active Devices : 4
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 1

         Layout : left-symmetric
     Chunk Size : 64K

  Delta Devices : 1, (4->5)

           UUID : 4fbdc8df:07b952cf:7cc6faa0:04676ba5
         Events : 0.683478

    Number   Major   Minor   RaidDevice State
       0       8       32        0      active sync   /dev/sdc
       1       8       48        1      active sync   /dev/sdd
       2       8       64        2      active sync   /dev/sde
       3       8       80        3      active sync   /dev/sdf
       4       0        0        4      removed

       5       8       16        -      spare   /dev/sdb

************************************************************************************
Anybody know what i need to do for /dev/sdb became ACTIVE DEVICE ?
************************************************************************************



**
@raid01:/# mdadm -E /dev/sdb
/dev/sdb:
          Magic : a92b4efc
        Version : 00.91.00
           UUID : 4fbdc8df:07b952cf:7cc6faa0:04676ba5
  Creation Time : Tue Nov 13 18:42:36 2007
     Raid Level : raid5
  Used Dev Size : 488386496 (465.76 GiB 500.11 GB)
     Array Size : 1953545984 (1863.05 GiB 2000.43 GB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 1

  Reshape pos'n : 194537472 (185.53 GiB 199.21 GB)
  Delta Devices : 1 (4->5)

    Update Time : Tue Jan 29 02:05:52 2008
          State : clean
 Active Devices : 4
Working Devices : 5
 Failed Devices : 1
  Spare Devices : 1
       Checksum : 450cd41b - correct
         Events : 0.683482

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     5       8       16        5      spare   /dev/sdb

   0     0       8       32        0      active sync   /dev/sdc
   1     1       8       48        1      active sync   /dev/sdd
   2     2       8       64        2      active sync   /dev/sde
   3     3       8       80        3      active sync   /dev/sdf
   4     4       0        0        4      faulty removed
   5     5       8       16        5      spare   /dev/sdb


   

-- 
Best regards
 Andreas
 mailto:andre.s@j8.com.ru

Re: problem with spare, acive device, clean degrated, reshaip RADI5, anybody can help ?

[Neil Brown]

On Thursday January 31, andre.s@j8.com.ru wrote:
> Hello linux-raid.
> 
> i have DEBIAN.
> 
> raid01:/# mdadm -V
> mdadm - v2.6.4 - 19th October 2007
> 
> raid01:/# mdadm -D /dev/md1
> /dev/md1:
>         Version : 00.91.03
>   Creation Time : Tue Nov 13 18:42:36 2007
>      Raid Level : raid5
....
>   Delta Devices : 1, (4->5)

So the array is in the middle of a "reshape".

It should automatically complete...  Presumably it isn't doing that?

What does
   cat /proc/mdstat
say?

Where kernel log messages do you get when you assemble the array?


The spare device will not be added to the array until the reshape has
finished.

Hopefully you aren't using a 2.6.23 kernel?
That kernel had a bug which corrupted data when reshaping a degraded
raid5 array.

NeilBrown

Re[2]: problem with spare, acive device, clean degrated, reshaip RADI5, anybody can help ?

[Andreas-Sokov]

Здравствуйте, Neil.

Вы писали 4 февраля 2008 г., 03:44:21:

> On Thursday January 31, andre.s@j8.com.ru wrote:
>> Hello linux-raid.
>> 
>> i have DEBIAN.
>> 
>> raid01:/# mdadm -V
>> mdadm - v2.6.4 - 19th October 2007
>> 
>> raid01:/# mdadm -D /dev/md1
>> /dev/md1:
>>         Version : 00.91.03
>>   Creation Time : Tue Nov 13 18:42:36 2007
>>      Raid Level : raid5
> ....
>>   Delta Devices : 1, (4->5)

> So the array is in the middle of a "reshape".

> It should automatically complete...  Presumably it isn't doing that?

> What does
>    cat /proc/mdstat
> say?

raid01:/etc# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
md1 : active(auto-read-only) raid5 sdc[0] sdb[5](S) sdf[3] sde[2] sdd[1]
      1465159488 blocks super 0.91 level 5, 64k chunk, algorithm 2 [5/4] [UUUU_]

unused devices: <none>
raid01:/etc#


> Where kernel log messages do you get when you assemble the array?
into /var/log/messages (os is DEBIAN)
last messages after -A was :

==> /var/log/messages <==
Feb  4 02:39:53 raid01 kernel: RAID5 conf printout:
Feb  4 02:39:53 raid01 kernel:  --- rd:5 wd:4
Feb  4 02:39:53 raid01 kernel:  disk 0, o:1, dev:sdc
Feb  4 02:39:53 raid01 kernel:  disk 1, o:1, dev:sdd
Feb  4 02:39:53 raid01 kernel:  disk 2, o:1, dev:sde
Feb  4 02:39:53 raid01 kernel:  disk 3, o:1, dev:sdf
Feb  4 02:39:53 raid01 kernel: ...ok start reshape thread


> The spare device will not be added to the array until the reshape has
> finished.
ok. I think what such must was to be (excuse me for my bad english)
But when i did not see nothing about reshape (reshaping) in mdadm -D /dev/md1
this was confuse to me .

> Hopefully you aren't using a 2.6.23 kernel?
yep, i remember you alert to me about 2.6.23 kernel
raid01:/etc# uname -a
Linux raid01 2.6.22.16-6 #7 SMP Thu Jan 24 21:58:32 MSK 2008 i686 GNU/Linux
raid01:/etc#


> That kernel had a bug which corrupte ata when reshaping a degraded
> raid5 array.

> NeilBrown



-- 
С уважением,
 Andreas-Sokov                          mailto:andre.s@j8.com.ru

-
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

Re[2]: problem with spare, acive device, clean degrated, reshaip RADI5, anybody can help ?

[Andreas-Sokov]

Hi, Neil.

4 февраля 2008 г., 03:44:21:

> On Thursday January 31, andre.s@j8.com.ru wrote:
>> Hello linux-raid.
>> 
>> i have DEBIAN.
>> 
>> raid01:/# mdadm -V
>> mdadm - v2.6.4 - 19th October 2007
>> 
>> raid01:/# mdadm -D /dev/md1
>> /dev/md1:
>>         Version : 00.91.03
>>   Creation Time : Tue Nov 13 18:42:36 2007
>>      Raid Level : raid5
> ....
>>   Delta Devices : 1, (4->5)

> So the array is in the middle of a "reshape".

AND :
i use now version mdadm :
raid01:/etc# mdadm -V
mdadm - v2.6.4 - 19th October 2007

and in previous version DURING reshaping such information apper in mdadm -D command
Why not appear now ?
May be you return it back ?
And indicating about % of process reshaping ?

What you think about this ?

-- 
 Andreas-Sokov

-
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

Re: Re[2]: problem with spare, acive device, clean degrated, reshaip RADI5, anybody can help ?

[Neil Brown]

On Monday February 4, andre.s@j8.com.ru wrote:
> 
> raid01:/etc# cat /proc/mdstat
> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
> md1 : active(auto-read-only) raid5 sdc[0] sdb[5](S) sdf[3] sde[2] sdd[1]
              ^^^^^^^^^^^^^^^
>       1465159488 blocks super 0.91 level 5, 64k chunk, algorithm 2 [5/4] [UUUU_]
> 
> unused devices: <none>

That explains it.  The array is still 'read-only' and won't write
anything until you allow it to.
The easiest way is
  mdadm -w /dev/md1

That should restart the reshape.

NeilBrown