On Sat, 1 Apr 2000, Mike Bilow wrote:
On Fri, 31 Mar 2000, Michael wrote:
hmmm. the remirroring code is not very smart... as I recall it
does the remirroring in order .. i.e. md0, md1, etc... This would
imply that if you have a power fail or other crash that causes both
md's to
On Sun, 02 Apr 2000, Marc Haber wrote:
On Sat, 1 Apr 2000 12:44:49 +0200, you wrote:
It _is_ in the docs.
Which docs do you refer to? I must have missed this.
Section 6.1 in http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/
Didn't you actually mention it yourself ? :)
(don't remember -
pardon me?
On Sun, Apr 02, 2000 at 02:03:36AM +0200, Thomas Rottler wrote:
Hi!
I have an autodetecting RAID1 swap set. The kernel does so all the work for
me...
Thomas
--
Luca Berra -- [EMAIL PROTECTED]
Communication Media Services S.r.l.
hi, all,
please correct me if I am wrong.
can Ultra160 HD run on Ultra2 Controller with Ultra2 speed?!
I tried to put Ultra160 HD (Seagate 9G HD) on a Ultra2 controller
(Adaptec 3896N),
the SCSI BIOS detect the drive without errors.
when I tried to install RedHat 6.1 (2.2.12) or Mandrake 7.0
On Apr 1, 10:40pm, Theo Van Dinter wrote:
} Subject: RAID Devices and FS labels
On my home machine today, I decided to change how the filesystems are listed
in /etc/fstab from the standard /dev/name to FS labels:
LABEL=ROOT/ ext2defaults1 1
On Sun, 2 Apr 2000 15:28:28 +0200, you wrote:
On Sun, 02 Apr 2000, Marc Haber wrote:
On Sat, 1 Apr 2000 12:44:49 +0200, you wrote:
It _is_ in the docs.
Which docs do you refer to? I must have missed this.
Section 6.1 in http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/
Didn't you actually
On Sun, 02 Apr 2000, Marc Haber wrote:
[snip]
Yes, I did. However, I'd add a sentence mentioning that in this case
mkraid probably won't be destructive to the HOWTO. After the mkraid
warning, I aborted the procedure and started asking. I think this
should be avoided in the future.
I have
I'm in the process of upgrading another production system from old tools
to new and noticed that you can't do a "raidstop" unless there is a valid
raidtab. It seems to me that with a persistent superblock, this should
not be necessary. The same applies to raidstart. Unless there is some
On Sat, 1 Apr 2000, Chris Mauritz wrote:
Just thought you guys would find it amusing that this card
worked just fine with vanilla Redhat 6.1, but gives blue
screens with both NT4 and Win2K Server. Mylex swears it is
a hardware issue and is the result of bugs in the Intel Carmel
840 chipset. I
This of course suggests that the raidtab file is almost redundant itself and
could be replaced by command-line options to mkraid. mke2fs certainly
doesn't require an fstab entry for a filesystem before it can be created or
dealt with. raidtab should be a place to keep information in case the
It does Raid 0 and 1 as well as appending.
Note:
http://www7.tomshardware.com/storage/00q1/000329/index.html
... for Tom's review of the card (and how to make a RAID card from the
non-RAID card).
Agus Budy Wuysang wrote:
Ed Schernau wrote:
No, it seems that it DOES do hw RAID, but with no
Hi all,
Is there an easy way to copy the partition information from one disk to
another disk that is exactly the same size? I'm guessing a dd on the right
device might do this but the exact command would be appreciated.
My goal is to not have to manually fdisk multiple disks
Hi all,
I think my situation is the same as this "two failed disks" one but I
haven't been following the thread carefully and I just want to double check.
I have a mirrored RAID-1 setup between 2 disks with no spare disks.
Inadvertantly the machine got powered down without a
On Mon, 3 Apr 2000, Rainer Mager wrote:
I think my situation is the same as this "two failed disks" one but I
haven't been following the thread carefully and I just want to double check.
I have a mirrored RAID-1 setup between 2 disks with no spare disks.
Inadvertantly the
Hmm, well, I'm certainly not positive why it wouldn't boot and I don't have
the logs in front of me, but I do remember it saying that it couldn't mount
/dev/md1 and therefore had a panic during boot. My solution was to specify
the root device as /dev/sda1 instead of the configured /dev/md1 from
Hmm, well, I'm certainly not positive why it wouldn't boot and I don't have
the logs in front of me, but I do remember it saying that it couldn't mount
/dev/md1 and therefore had a panic during boot. My solution was to specify
the root device as /dev/sda1 instead of the configured /dev/md1
16 matches
Mail list logo
