- Original Message -
From: Neil Brown [EMAIL PROTECTED]
To: JaniD++ [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
Sent: Thursday, January 12, 2006 4:07 AM
Subject: Re: where is the spare drive? :-)
On Monday January 2, [EMAIL PROTECTED] wrote:
5. The question
Why shows sdh2
Matt Darcy wrote:
Jeff Garzik wrote:
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
to receive the following updates:
drivers/scsi/sata_nv.c | 30 --
1 files changed, 24 insertions(+), 6
Hello,
I've had a lot of problems with nv_sata (nforce3) and Maxtor harddrives.
Basically it always boils down to :
Dec 24 23:04:34 apollo13 ata3: command 0x35 timeout, stat 0xd0 host_stat
0x21
Dec 24 23:04:34 apollo13 ata3: translated ATA stat/err 0x35/00 to SCSI
SK/ASC/ASCQ
[EMAIL PROTECTED] wrote:
snip - a lot!!
can I summarise (!) as:
I want to create a non-system data-storage raid array (ie can be
initialised well after boot)
I want to use a mix of SCSI, sata + USB devices
Will this work if the USB devices change their 'order'
Short answer: yes, with the
I can now provide further updates for this, although this are not
really super useful.
I've copied the linux-raid list in as well, as after a little more
testing on my part I'd appriciate some input from the raid guys also.
First of all, please ignore the comments above, there was a
Hi all,
1- I would like to create a linear raid level with one device. (or with
raid0)
2- I would like to add another device to the first one.
Anyone knows how ?
Martin
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More
Also if i do something like:
# grow bad blocks as ma*tor does :)
mdadm --grow -l faulty -p rp454 /dev/md2
mdadm --grow -l faulty -p rp738 /dev/md3
# add a spare
mdadm -a /dev/md5 /dev/ram5
mdadm -f /dev/md5 /dev/md2 mdadm -f /dev/md5 /dev/md2
After the initial reconstruction i get this:
On Thu, Jan 12, 2006 at 11:16:36AM +, David Greaves wrote:
ok, first off: a 14 device raid1 is 14 times more likely to lose *all*
your data than a single device.
No, this is completely incorrect. Let A denote the event that a single
disk has failed, A_i denote the event that i disks have
On Thu, Jan 12 2006, Jurriaan on adsl-gate wrote:
From: Neil Brown [EMAIL PROTECTED]
Date: Thu, Jan 12, 2006 at 05:36:42PM +1100
Sent-To:
On Thursday January 12, [EMAIL PROTECTED] wrote:
2.6.15-mm3 hangs during boot for me, after the lines
md4: bitmap initialized
Hello, list,
I have found one interesting issue.
I use 4 disk node with NBD, and the concentrator distributes the load equal
thanks to 32KB chunksize RAID0 inside.
At this time i am working on the system upgrade, and found one interesting
issue, and possibly one bottleneck on the system.
The
10 matches
Mail list logo