On Sat, 10 Feb 2007, Eyal Lebedinsky wrote:
I have a six-disk RAID5 over sata. First two disks are on the mobo and last four
are on a Promise SATA-II-150-TX4. The sixth disk was added recently and I
decided
to run a 'check' periodically, and started one manually to see how long it
should
Raz Ben-Jehuda(caro) wrote:
On 2/10/07, Eyal Lebedinsky [EMAIL PROTECTED] wrote:
I have a six-disk RAID5 over sata. First two disks are on the mobo and
last four
are on a Promise SATA-II-150-TX4. The sixth disk was added recently
and I decided
to run a 'check' periodically, and started one
Justin Piszcz wrote:
On Sat, 10 Feb 2007, Eyal Lebedinsky wrote:
I have a six-disk RAID5 over sata. First two disks are on the mobo and
last four
are on a Promise SATA-II-150-TX4. The sixth disk was added recently
and I decided
to run a 'check' periodically, and started one manually to
On Sat, 10 Feb 2007, Eyal Lebedinsky wrote:
Justin Piszcz wrote:
On Sat, 10 Feb 2007, Eyal Lebedinsky wrote:
I have a six-disk RAID5 over sata. First two disks are on the mobo and
last four
are on a Promise SATA-II-150-TX4. The sixth disk was added recently
and I decided
to run a 'check'
On Sat, Jan 27, 2007 at 02:59:48AM +0100, Iustin Pop wrote:
From: Iustin Pop [EMAIL PROTECTED]
This patch exposes the uuid and the degraded status of an assembled
array through sysfs.
[...]
Sorry to ask, this was my first patch and I'm not sure what is the
procedure to get it considered for
Iustin Pop wrote:
On Sat, Jan 27, 2007 at 02:59:48AM +0100, Iustin Pop wrote:
From: Iustin Pop [EMAIL PROTECTED]
This patch exposes the uuid and the degraded status of an assembled
array through sysfs.
[...]
Sorry to ask, this was my first patch and I'm not sure what is the
procedure
Hi,
I just tried to setup a one-device raid onto an USB flash drive.
Creating, setting up ext3 and filling with data was no problem.
But when I tried to work with it afterwards the metadevice was
unresponsive. I tried both linear and raid0 levels, but that
made no difference.
For my uneducated
Arne Jansen wrote:
The main reason why I'm trying this weird setup is that the USB
drive is always enumerated last in my kernel, and I want to boot
from it. That means every time I add a disk or remove one I have
to edit grub.conf and fstab. Very inconvenient. So my idea was
to create a
Raz Ben-Jehuda(caro) wrote:
On 2/10/07, Eyal Lebedinsky [EMAIL PROTECTED] wrote:
I have a six-disk RAID5 over sata. First two disks are on the mobo
and last four
are on a Promise SATA-II-150-TX4. The sixth disk was added recently
and I decided
to run a 'check' periodically, and started one
Justin Piszcz wrote:
On Sat, 10 Feb 2007, Eyal Lebedinsky wrote:
Justin Piszcz wrote:
On Sat, 10 Feb 2007, Eyal Lebedinsky wrote:
I have a six-disk RAID5 over sata. First two disks are on the mobo and
last four
are on a Promise SATA-II-150-TX4. The sixth disk was added recently
and I
On Saturday February 10, [EMAIL PROTECTED] wrote:
Iustin Pop wrote:
On Sat, Jan 27, 2007 at 02:59:48AM +0100, Iustin Pop wrote:
From: Iustin Pop [EMAIL PROTECTED]
This patch exposes the uuid and the degraded status of an assembled
array through sysfs.
[...]
Sorry to
On Sun, Feb 11, 2007 at 08:15:31AM +1100, Neil Brown wrote:
Resending after a suitable pause (1-2 weeks) is never a bad idea.
Ok, noted, thanks.
Exposing the UUID isn't - and if it were it should be in
md_default_attrs rather than md_redundancy_attrs.
The UUID isn't an intrinsic aspect of
On Sun, 11 Feb 2007 09:59:29 +0300, Michael Tokarev wrote:
Marco Scoffier wrote:
Hello all,
I have an old raid0 with no superblocks.
Well, mdadm is able to assemble it. It's called 'build' (--build) --
mdadm --build -n 2 -c 128 -l 0 /dev/md0 /dev/hde1 /dev/hdg1
Thanks for the
Greetings,
I've been running md on my server for some time now and a few days ago one of
the (3) drives in the raid5 array starting giving read errors. The result was
usually system hangs and this was with kernel 2.6.17.13. I upgraded to the
latest production 2.6.20 kernel and experienced the
14 matches
Mail list logo
