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

2008-02-03 Thread Andreas-Sokov 
Здравствуйте, Neil.

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

 On Thursday January 31, [EMAIL PROTECTED] 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] [_]

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:[EMAIL PROTECTED]

-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
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 ?

2008-02-03 Thread Andreas-Sokov 
Hi, Neil.

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

 On Thursday January 31, [EMAIL PROTECTED] 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 [EMAIL PROTECTED]
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 ?

2008-02-03 Thread Neil Brown 
On Monday February 4, [EMAIL PROTECTED] 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] 
 [_]
 
 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
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html