tmp [EMAIL PROTECTED] wrote:
I've read man mdadm and man mdadm.conf but I certainly doesn't have
an overview of software RAID.
Then try using it instead/as well as reading about it, and you will
obtain a more cmprehensive understanding.
OK. The HOWTO describes mostly a raidtools context,
On Mon, Apr 18, 2005 at 08:05:22PM -0500, John McMonagle wrote:
Luca Berra wrote:
On Sun, Apr 17, 2005 at 05:04:13PM -0500, John McMonagle wrote:
Need to duplicate some computers that are using raid 1.
I was thinking of just adding adding an extra drive and then moving
it to the new system. The
Luca Berra wrote:
many people find it easier to understand if raid partitions are set to
0XFD. kernel autodetection is broken and should not be relied upon.
Could you clarify what is broken?
I understood that it was simplistic (ie if you have a raid0 built over a
raid5
or something exotic then it
At Sun, 17 Apr 2005 12:51:03 -0400,
TJ wrote:
I was using the 2.6.7 kernel without APIC or ACPI support, and the via82xx
driver worked perfectly, compiled as a module, without any options. I built a
new 2.6.7 kernel on the same hardware with APIC and ACPI support in the
kernel, as the
On Sun, Apr 17, 2005 at 10:49:14AM -0700, Tim Moore wrote:
Hi,
The recovery daemon adjusts reconstruction speed dynamically according to
available system resources.
Disk I/O is somewhat slower but works just fine. You don't have to wait.
So I don't have to wait to take the disk out, as
Devid wrote:
5) Removing a disk requires that I do a mdadm -r on all the
partitions
that is involved in a RAID array. I attempt to by a hot-swap capable
controler, so what happens if I just pull out the disk without this
manual removal command?
as far as md is concerned the disk
Hervé Eychenne wrote:
On Sun, Apr 17, 2005 at 10:49:14AM -0700, Tim Moore wrote:
The recovery daemon adjusts reconstruction speed dynamically according to
available system resources.
Disk I/O is somewhat slower but works just fine. You don't have to wait.
So I don't have to wait to take the
A followup about one single question.
tmp wrote:
[]
Is it correct that I can use whole disks (/dev/hdb) only if I make a
partitionable array and thus creates the partitions UPON the raid
mechanism?
Just don't use whole disks for md arrays. *Especially* if you want
to create partitions inside the
David Greaves wrote:
Luca Berra wrote:
many people find it easier to understand if raid partitions are set to
0XFD. kernel autodetection is broken and should not be relied upon.
Could you clarify what is broken?
I understood that it was simplistic (ie if you have a raid0 built over a
raid5
or
David Greaves wrote:
Does everyone really type cat /proc/mdstat from time to time??
How clumsy...
And yes, I do :)
You're not alone..
*gah...*
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Tue, 19 Apr 2005, Molle Bestefich wrote:
David Greaves wrote:
Does everyone really type cat /proc/mdstat from time to time??
How clumsy...
And yes, I do :)
You're not alone..
and it's still a lot better than some of the hw raid monitoring tools
- more data
- more
On Tue, Apr 19, 2005 at 01:00:11PM +0200, [EMAIL PROTECTED] wrote:
You have to mdadm -r remove it and re-add it once you restore the disk.
First you have to look if there are partitions on that disk to which no
data was written since the disk failed (this typically concerns the swap
Hervé Eychenne wrote:
On Tue, Apr 19, 2005 at 01:00:11PM +0200, [EMAIL PROTECTED] wrote:
First you have to look if there are partitions on that disk to which no
data was written since the disk failed (this typically concerns the swap
partition). These partitions have to be marked faulty by hand
On Tue, Apr 19, 2005 at 04:27:14PM +0100, David Greaves wrote:
Hervé Eychenne wrote:
On Tue, Apr 19, 2005 at 01:00:11PM +0200, [EMAIL PROTECTED] wrote:
First you have to look if there are partitions on that disk to which no
data was written since the disk failed (this typically concerns the
Hervé Eychenne wrote:
And those who do can type:
fdisk -l /dev/sda | grep -i fd | cut -f1 -d' ' | xargs -n1 mdadm -r
I really don't like kludgy things like that...
[...]
Isn't the insertion/removal of a disk common enough to justify the
addition of a simple and clean mdadm option?
have
On Tue, Apr 19, 2005 at 06:53:52PM +0200, Frank Wittig wrote:
And those who do can type:
fdisk -l /dev/sda | grep -i fd | cut -f1 -d' ' | xargs -n1 mdadm -r
I really don't like kludgy things like that...
[...]
Isn't the insertion/removal of a disk common enough to justify the
Hervé Eychenne wrote:
Maybe you are an experienced guy so it seems so simple to you... but
I'm always amused when an experienced guy refuses to make things
simpler for those who aren't as much as he is. And sends them to
Microsoft. Great.
i don't send you to microsoft. i want you to
-Original Message-
From: [EMAIL PROTECTED] [mailto:linux-raid-
[EMAIL PROTECTED] On Behalf Of Frank Wittig
Sent: Tuesday, April 19, 2005 3:47 PM
To: [EMAIL PROTECTED]
Cc: linux-raid@vger.kernel.org
Subject: Re: Questions about software RAID
Hervé Eychenne wrote:
Maybe you
On Wed, 20 Apr 2005, Guy wrote:
Well, I agree with KISS, but from the operator's point of view!
I want the failed disk to light a red LED.
I want the tray the disk is in to light a red LED.
I want the cabinet the tray is in to light a red LED.
I want the re-build to the spare to start.
I
19 matches
Mail list logo
