linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: rbroman@bayarea.net
Cc: linux-ide@vger.kernel.org
Subject: Re: Software RAID Problem
Date: Wed, 29 Jul 2009 11:09:24 +0900	[thread overview]
Message-ID: <4A6FAF54.1060902@kernel.org> (raw)
In-Reply-To: <1248798289.4a6f26510c218@myaccount.bayarea.net>

Hello,

When you reply further, can you please do the followings?

1. Don't drop cc list.

2. Use an email client which properly specifies References: and
   In-Reply-To:.

rbroman@bayarea.net wrote:
>> Can you attach full output of 'dmesg' after raid degradation?
> 
> For context, there are four RAID devices on this system. md0 is
> /boot, md1 is / and md2 and md3 are the problem devices. /proc/mdstat
> is below followed by the output of dmesg.
> 
> /proc/mdstat
> 
> Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
> [raid10]
> md_d3 : inactive sdd2[2](S)
>       366289920 blocks
> 
> md_d2 : inactive sdd1[2](S)
>       366281856 blocks
> 
> md1 : active raid0 sdb6[1] sda6[0]
>       781256704 blocks 64k chunks
> 
> md0 : active raid1 sda1[0] sdb1[1]
>       48829440 blocks [2/2] [UU]
> 
> unused devices: <none>
> 
> dmesg .....
> 

The dmesg doesn't contain ATA error messages and the actual
degradation.  Can you please trigger that and then attach dmesg?

Thanks.

-- 
tejun

  reply	other threads:[~2009-07-29  2:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 16:24 Software RAID Problem rbroman
2009-07-29  2:09 ` Tejun Heo [this message]
2009-07-29 15:40   ` Randy Broman
2009-07-29 19:40     ` Robert Hancock
2009-07-29 20:43       ` Randy Broman
  -- strict thread matches above, loose matches on Subject: below --
2009-07-27 20:27 Randy Broman
2009-07-28  3:19 ` Tejun Heo

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=4A6FAF54.1060902@kernel.org \
    --to=tj@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=rbroman@bayarea.net \
    /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).