linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Marc Marais" <marcm@liquid-nexus.net>
To: linux-raid@vger.kernel.org
Subject: Fw: Re: mdadm --grow failed
Date: Sun, 18 Feb 2007 19:57:28 +0800	[thread overview]
Message-ID: <20070218115626.M47438@liquid-nexus.net> (raw)
In-Reply-To: <20070218105242.M29958@liquid-nexus.net>

On Sun, 18 Feb 2007 20:39:09 +1100, Neil Brown wrote
> On Sunday February 18, marcm@liquid-nexus.net wrote:
> > Ok, I understand the risks which is why I did a full backup before doing 
> > this. I have subsequently recreated the array and restored my data from 
> > backup.
> 
> Could you still please tell me exactly what kernel/mdadm version you
> were using?
> 
> Thanks,
> NeilBrown

2.6.20 with the patch you supplied in response to the "md6_raid5 crash 
email" I posted in linux-raid a few days ago. Just as background, I replaced 
the failing drive and at the same time bought an additional drive in order 
to increase the array size.

mdadm -V = v2.6 - 21 December 2006. Compiled under Debian (stable).

Also, I've just noticed another drive failure with the new array with a 
similar error to what happened during the grow operation (although on a 
different drive) - I wonder if I should post this to linux-ide?

Feb 18 00:58:10 xerces kernel: ata4: command timeout
Feb 18 00:58:10 xerces kernel: ata4: no sense translation for status: 0x40
Feb 18 00:58:10 xerces kernel: ata4: translated ATA stat/err 0x40/00 to SCSI 
SK/ASC/ASCQ 0xb/00/00
Feb 18 00:58:10 xerces kernel: ata4: status=0x40 { DriveReady }
Feb 18 00:58:10 xerces kernel: sd 4:0:0:0: SCSI error: return code = 
0x08000002
Feb 18 00:58:10 xerces kernel: sdd: Current [descriptor]: sense key: Aborted 
Command
Feb 18 00:58:10 xerces kernel:     Additional sense: No additional sense 
information
Feb 18 00:58:10 xerces kernel: Descriptor sense data with sense descriptors 
(in hex):
Feb 18 00:58:10 xerces kernel:         72 0b 00 00 00 00 00 0c 00 0a 80 00 
00 00 00 00
Feb 18 00:58:10 xerces kernel:         00 00 00 00
Feb 18 00:58:10 xerces kernel: end_request: I/O error, dev sdd, sector 
35666775
Feb 18 00:58:10 xerces kernel: raid5: Disk failure on sdd1, disabling 
device. Operation continuing on 3 devices

Regards,
Marc


  parent reply	other threads:[~2007-02-18 11:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17  3:22 mdadm --grow failed Marc Marais
2007-02-17  8:40 ` Neil Brown
2007-02-18  9:20   ` Marc Marais
     [not found]     ` <17880.7869.963793.706096@notabene.brown>
     [not found]       ` <20070218105242.M29958@liquid-nexus.net>
2007-02-18 11:57         ` Marc Marais [this message]
2007-02-18 12:13           ` Fw: " Justin Piszcz
2007-02-18 12:32             ` Marc Marais
2007-02-19  5:41             ` Marc Marais
2007-02-19 13:25               ` Justin Piszcz
2007-02-19  0:50     ` Neil Brown
2007-02-17 18:27 ` Bill Davidsen
2007-02-17 19:16   ` Justin Piszcz
2007-02-17 21:08     ` Neil Brown
2007-02-17 21:30       ` Justin Piszcz
2007-02-18 11:51 ` David Greaves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070218115626.M47438@liquid-nexus.net \
    --to=marcm@liquid-nexus.net \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).