All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@mvista.com>
To: "SCHEP. - Schepke, Arnt" <SCHEP@Hoeft-Wessel.de>
Cc: "'linux-raid@vger.kernel.org'" <linux-raid@vger.kernel.org>
Subject: Re: SW-RAID 1 and kernel 2.4.18
Date: Tue, 26 Nov 2002 12:33:33 -0700	[thread overview]
Message-ID: <3DE3CC8D.2080104@mvista.com> (raw)
In-Reply-To: 984305F1827DD5118FEA0000D1105F0A01BDC029@HW_MAIL

Schep,

IDE was not designed to hotswap.  The trays are not "hot swappable" in 
that they can only be swapped while the system is off.

For hotswap support, look to SCSI or even better, FibreChannel.  These 
systems are designed to be electrically safe in hotswap operations and 
maintain the integrity of the data transfers.

Thanks
-steve

SCHEP. - Schepke, Arnt wrote:

>Hi, i have a running software raid 1. This consist of two ide devices hda
>and hdc. The root filesystem is running on this raid array. The harddiscs
>are installed in removable frames. 
>The system seems to work correctly. But i get some errors. In the file
>messages i found: 
>
>linux kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } 
>linux kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC }
>
>Are the removables frames my problem? If i remove the frames (connect the
>ide direct to the cable) the system runs better. I could not find the
>message above. 
>
>If i start a stress test (lot of file copies) the raid array starts
>sometimes a resync process. I can't find more information at messages-file. 
>
>Where does this come from? Where i have to look to get information to
>prevent this? And at last the system warns me at restart that my
>raid-superblocks are not correct. 
>
>How do i resolve this? 
>If i connect the two ide devices to the same ide port (hda and hdb used for
>raid array) i also get a message about invalid raid superblocks. 
>
>Someone knows something about this?
>
>Regards
>
>Arnt Schepke
>
>
>-
>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
>
>
>
>  
>


  reply	other threads:[~2002-11-26 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26 13:56 SW-RAID 1 and kernel 2.4.18 SCHEP. - Schepke, Arnt
2002-11-26 19:33 ` Steven Dake [this message]
2002-11-26 22:52   ` H. Peter Anvin
2002-11-26 23:05     ` Alvin Oga
2002-12-03 16:01 ` some IDE trays are bad (was Re: SW-RAID 1 and kernel 2.4.18) Louis-David Mitterrand
2002-12-03 21:06   ` Maurice Hilarius
2002-12-03 22:10   ` Gregory Leblanc

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=3DE3CC8D.2080104@mvista.com \
    --to=sdake@mvista.com \
    --cc=SCHEP@Hoeft-Wessel.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.