Gerd Knops wrote:
Hello all,
One of the dreaded Maxtor SATA drives in my RAID5 failed, after just 3
months of light use. Anyhow I neither have the disk capacity nor the
money to buy it to make a backup. To make sure I do it correctly, could
you folks please double-check my intended course of
Mike Hardy wrote:
Gerd Knops wrote:
Hello all,
One of the dreaded Maxtor SATA drives in my RAID5 failed, after just 3
months of light use. Anyhow I neither have the disk capacity nor the
money to buy it to make a backup. To make sure I do it correctly,
could you folks please double-check my
Neil Brown wrote:
If you are using a recent 2.6 kernel and mdadm 1.8.0, you can grow the
array with
mdadm --grow /dev/mdX --size=max
Neil,
Is this just for RAID1? OR will it work for RAID5 too?
R.
--
http://robinbowes.com
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
Luca Berra wrote:
On Tue, Feb 01, 2005 at 03:02:54PM +, Robin Bowes wrote:
True enough. However, until SMART support makes it into linux SATA
drivers I'm pretty much stuck with dd!
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/
I avoid patching kernels, preferring to use
Hi,
I run a RAID5 array built from six 250GB Maxtor Maxline II SATA disks.
After having several problems with Maxtor disks I decided to use a spare
disk, i.e. 5+1 spare.
Well, *another* disk failed last week. The spare disk was brought into
play seamlessly:
[EMAIL PROTECTED] ~]# mdadm
Nicola Fankhauser wrote:
see [3] for a description of what I did and more details.
Hi Nicola,
I read your description with interest.
I thought I'd try some speed tests myself but dd doesn't seem to work
the same for me (on FC3). Here's what I get:
[EMAIL PROTECTED] test]# dd if=/dev/zero
Robin Bowes wrote:
If I try to start the array manually:
# mdadm --assemble --auto=yes /dev/md2 /dev/hdc /dev/hdd /dev/hde
/dev/hdf /dev/hdg /dev/hdh /dev/hdi /dev/hdj
mdadm: cannot open device /dev/hdc: No such file or directory
mdadm: /dev/hdc has no superblock - assembly aborted
Robin Bowes wrote:
This worked:
# mdadm --assemble --auto=yes /dev/md2 /dev/sdc /dev/sdd /dev/sde
/dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj
mdadm: /dev/md2 has been started with 8 drives.
However, I'm not sure why it didn't start automatically at boot. Do I
need to put it in /etc
Robin Bowes wrote:
Robin Bowes wrote:
This worked:
# mdadm --assemble --auto=yes /dev/md2 /dev/sdc /dev/sdd /dev/sde
/dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj
mdadm: /dev/md2 has been started with 8 drives.
However, I'm not sure why it didn't start automatically at boot. Do I
need
Robin Bowes wrote:
Well, at the risk of having a complete conversation with myself, I've
created partitions of type fd on each disk and re-created the array
out of the partitions instead of the whole disk.
mdadm --create /dev/md2 --auto=yes --raid-devices=8 --level=6 /dev/sdc1
/dev/sdd1
Bill Davidsen wrote:
There have been several recent threads on the list regarding software
RAID-5 performance. The reference might be updated to reflect the poor
write performance of RAID-5 until/unless significant tuning is done.
Read that as tuning obscure parameters and throwing a lot of
Bill Davidsen wrote:
Robin Bowes wrote:
Bill Davidsen wrote:
There have been several recent threads on the list regarding software
RAID-5 performance. The reference might be updated to reflect the poor
write performance of RAID-5 until/unless significant tuning is done.
Read
12 matches
Mail list logo
