On Sep 15, 2:01pm, Chris Mauritz wrote:
} Subject: Re: Newbie: What to do when a disk fails?
> > This all pretty much implies that a new RAID patchset will be required
> > when 2.2.13 hits the streets.
>
> Sigh. So what do the RAID deities suggest someone use for "p
My problem seemed to precede an application of raidsetfaulty (if I
understand its function), thus:
(1) I removed a disk to simulate disk failure. The RAID did not
notice. (Even doing reads may not make it notice, presumably because
of buffering.)
(2) I did a dd if=/dev/md0 way out of range
[ Wednesday, September 15, 1999 ] Lawrence Dickson wrote:
>raidhotremove seems to THINK it can work without unmounting
> the raid array fs... same with the echo to /proc/scsi/scsi ...
> it's really all just syncing code, isn't it, guys?
I've been curious what raidsetfaulty would do (if anythi
All,
I appreciate the amount of play my "newbie" question has
had, and have the feeling we are teetering an inch from an
answer. I've got to leap that inch - the infuriating
alternative is that our whole Linux-RAID development gets
tossed and replaced with antediluvian hardware RAID at
trem
On Tue, 14 Sep 1999, Lawrence Dickson wrote:
So I take it the 18 disk RAID has to be unmounted before I
can do this. That's a killer.
eek, i was tired.. i didn't mean to say raidstop - sorry. The array
doesn't need to be stopped if it's a fault tolerant array. So should
be:
The *disk to
> From [EMAIL PROTECTED] Wed Sep 15 13:50:22 1999
>
> Good morning to everyone.
>
> > correct me if I'm wrong, but I think the current recipe is patching 2.2.12
> > with the latest raid alpha patch (for 2.2.11) and when patch complains
> > about fs.h, tell it to completely skip fs.h since change
On Sep 14, 4:57pm, David Holl wrote:
} Subject: Re: Newbie: What to do when a disk fails?
Good morning to everyone.
> correct me if I'm wrong, but I think the current recipe is patching 2.2.12
> with the latest raid alpha patch (for 2.2.11) and when patch complains
> about fs
correct me if I'm wrong, but I think the current recipe is patching 2.2.12
with the latest raid alpha patch (for 2.2.11) and when patch complains
about fs.h, tell it to completely skip fs.h since changes to that file are
already in 2.2.12
is there a specific reason the raid patches are in the alp
All,
Well, unmounting our RAID (which is using the disk) is not
acceptable, since there will be a bunch of NFS and Samba
shares hanging off it at all times. So (groan) I guess I do
need the latest and greatest. Can someone point me to the
right recipe for going straight from RedHat 6.0 (2.2.
On Mon, 13 Sep 1999, Lawrence Dickson wrote:
>1. unmount everything that's directly on the disk that isn't raid.
>2. swapoff if you have swap on that disk
Didn't understand this. Our system is on hda and we can't
unmount it.
indeed. you can't do it on the disk with the root-device on
All,
Here's a reprise of this ancient message. But there's method
in my madness. We need to do just this and are hitting a wall.
We have stock RedHat 6.0 with the 18 disk patch by Lance
Robinson, and no other kernel, module or raidtools changes. We
tried removing disk fifteen (sdo, scsi 2 0
t: Thursday, July 08, 1999 3:40 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Newbie: What to do when a disk fails?
>
[clip]
> I notice when I reboot, that the drive inserted spins up. Normally,
> when
> the machine is switched on, the
> drives spin up when the scs
Paul Jakma wrote:
> echo "scsi add-single-device c b t l" > /proc/scsi/scsi
I've tried this:
Insert 4 disks in system, 1 root, 3 in raid-5.
The raid is up and running.
I remove one of the disks in the raid (yes, they are supposed to
be hot plugable...).
The raid complains, and continues
On 7 Jul 1999, m.allan noah wrote:
> 5. Reboot to get linux to recognize the new partition
you hit the nail on the head man. no need to copy things to the replacement
disk. just get the partition table right and readable by linux (requires the
reboot in 5). then use raidhotadd.
reboot
> I suspect thst I could have done something like this:
>
> 1. Remove the failed disk.
> 2. Insert a new one
> 3. Boot with only one disk set up for raid usage.
> 4. Use fdisk to get the partition table right.
> 5. Reboot to get linux to recognize the new partition
> 6. Use raidhotadd toadd the
I have a follow up question:
I have a Compaq server running Redhat 6.0, with hot-swapable root disks, that
I've set up to use a raid-1 root disk. (by kreating a new bootimage with the
raid-1 loadable module included).
Yesterday one of the two disks included in the raid-1 had some problems.
After
16 matches
Mail list logo
