Thanks,
the hot-swap on IDE disks really works. I disconnected one of the IDE
cables
to create a failed disk. After that I wanted to get the disk back in the
array without a reboot of the system. One of you gave me the advice to
do a "raidhotremove" first and after that the "raidhotadd". And
On 22-Apr-99 Paul Jakma wrote:
Ok I ran a few bonnies with differenc chunk sizes...
Raid5 running on 4 WDC AC31300R's UDMA... Seems to peak at 32k chunks, 4K block
size
Thanks for your replies...
Cheers (time to do the "power removal" test :) )
--
John Ronan [EMAIL PROTECTED],
I'm looking for a way of removing active disks from a RAID1 without
disconnecting the drive or making any of the other paritions on the disk
inaccessible.
I think the best way to do this would be to get the md driver to believe
the disk had failed. There seems to be no way of doing this with the
This brings up another question, partitioning. The above (I don't think)
would work currently
anyway due to the disks having to be partitioned out first (correct?). How
hard would it be
to have the raid code itself write the required partition information and
whatever it requires
to get
On Mon, 26 Apr 1999, Benno Senoner wrote:
I am interested more in the idea of automatically repartition a new blank disk
while it is hot-added.
no need to do this in the kernel (or even in raidtools). I use such
scripts to 'mass-create' partitioned disks:
[root@moon root]# cat dobigsd
if
Hi,
On Sat, 24 Apr 1999 21:09:05 +0200 (MEST), Francisco Jose Montilla
[EMAIL PROTECTED] said:
Hi, I happen to came across a couple of statements that somewhat
involves the use of RAID, statements that I believe are not absolutely
correct, if not false, or half truths.
---
On Fri, 23 Apr 1999, John Ronan wrote:
On 22-Apr-99 Paul Jakma wrote:
Ok I ran a few bonnies with differenc chunk sizes...
Raid5 running on 4 WDC AC31300R's UDMA... Seems to peak at 32k
chunks, 4K block size
i've done a bit of benching aswell. The most important (on ia32
Ingo Molnar wrote:
On Mon, 26 Apr 1999, Benno Senoner wrote:
I am interested more in the idea of automatically repartition a new blank disk
while it is hot-added.
no need to do this in the kernel (or even in raidtools). I use such
scripts to 'mass-create' partitioned disks:
that's ok,
Hi,
On Thu, 22 Apr 1999 20:45:52 +0100 (IST), Paul Jakma [EMAIL PROTECTED]
said:
i tried this with raid0, and if bonnie is any guide, the optimal
configuration is 64k chunk size, 4k e2fs block size.
Going much above 64k will mean that readahead has to work very much
harder to keep all the
On Mon, 26 Apr 1999, Benno Senoner wrote:
no need to do this in the kernel (or even in raidtools). I use such
scripts to 'mass-create' partitioned disks:
but it's not unsafe to overwrite the partition-table of disks which are
actually part of a soft-raid array and in use ?
it's
Ingo Molnar wrote:
On Mon, 26 Apr 1999, Benno Senoner wrote:
no need to do this in the kernel (or even in raidtools). I use such
scripts to 'mass-create' partitioned disks:
but it's not unsafe to overwrite the partition-table of disks which are
actually part of a soft-raid array
Hi,
On Mon, 26 Apr 1999 21:28:20 +0100 (IST), Paul Jakma [EMAIL PROTECTED]
said:
it was close between 32k and 64k. 128k was noticably slower (for
bonnie) so i didn't bother with 256k.
Fine, but 128k will be noticeably faster for some other tasks. Like I
said, it depends on whether you
"McGee, Chris" wrote:
Hallo-
In the wake of a friend's recent LILO problems (plus that Chernobyl
thing for the dual-booters amongst us, I suppose), I've got a couple
questions regarding the preservation of a disks or md set's MBR.
What is the proper way to preserve the
13 matches
Mail list logo
