>
> Humm, did you test it (by unplugging the sda disk and booting) ?
>
Yes, worked just fine. The raid code figured out that the device (now
/dev/sda3) used to be /dev/sdb3, updated the superblock accordingly, and
continued in degraded mode.
> If you didn't you might be in for a surprise...
>
>
Michael Milligan wrote:
> To add a little bit of thinking on /boot... I have a small ext2fs partition
> (/dev/sda1) which is mounted as /boot that is not raid. That same partition
> is mirrored (manually) as /dev/sdb1, and I instructed lilo to install a boot
> block in the MBR of /dev/sdb. Thi
A James Lewis <[EMAIL PROTECTED]> wrote:
>
> I posted this a while back, I think some people found it usefull... so
> here goes again
>
Thanks for taking the time to write up this cookbook (included at the end
for folks who missed it), it sure looks like FAQ material to me. It's
relatively
My initial suspect would be that it seems very unlikley that the 19990713
patch (intended for 2.2.10) would apply cleanly to 2.2.5.
however, you probably also need to make sure that the raidtools version
supplied with redhat is not installed (and possibly earlier on your
path).
Also, wh
I tried this, and I 'm having trouble. Any help would be appreciated...
I am running stock RedHat 6.0 with Kernel 2.2.5-15 recompiled and patched with
raid0145-19990713.
I am also running raidtools-19990713. I get to where I mkraid and this is what
I get:
# mkraid /dev/md0
DESTROYING the content
Apparently it's included in the new raidtools released today...
On Wed, 14 Jul 1999, EMC Computers wrote:
>
>
> > -- Forwarded message --
> > Date: Fri, 09 Jul 1999 12:49:10 +0100
> > From: A James Lewis <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]
> > Subject: Linux root
On Wed, 14 Jul 1999, EMC Computers wrote:
> I would like to give this a try. Does anyone know where I can find the
> failed disk patch?
it's included in the 19990713 release.
-- mingo
> -- Forwarded message --
> Date: Fri, 09 Jul 1999 12:49:10 +0100
> From: A James Lewis <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Linux root mirror
>
> This guide assumes that there are two disks hda & hdc, and that "/" is
> /dev/hda2
>
> It also assumes that /boot (
I posted this a while back, I think some people found it usefull... so
here goes again
Since I wrote this however I have decided that it makes sense if possible
to use device numbers for raid that are the same as the partitions they
are built from for ease of maintainance!
So that a mirror
Yeah, other people have said that too I guess I'm just set in my
ways!!
Otherwise it went smoothly, that was the first time I used Martin Bene's
patches and I did the recipie on a different window while I was doing
it... Oh the machine in question is about 15 miles away from here.. it's
just
On Fri, Apr 23, 1999 at 02:36:25PM +0100, A James Lewis wrote:
>
Hi!
Just one minor suggestion:
> 5. Copy filesystem to new array, mounted on /mnt.
>
> moo:/# for i in `ls | grep -v mnt | grep -v proc`
> > do
> > cp -dpR $i /mnt
> > done
>
I do this by:
cd /
find . -xdev | cpio -pm /mnt
This guide assumes that there are two disks hda & hdc, and that "/" is
/dev/hda2
It also assumes that /boot (The kernel) is NOT on /. /boot requires
special handling but I suggest simply maintaining a copy on both disks
until LILO is raid aware.
This example was done with Martin Bene's failed
12 matches
Mail list logo
