headers
ALOE VERA | 1 Jan 2004 16:30

KENDI ISINIZI KURUN !!!

Iyi gunler linux-raid ,

Dnyanin en hizli byyen pazarinda

kendi isinizi kurup,
evinizden veya ofisinizden,
kendi patrononuz olarak tamamen bagimsiz,
calisma saatlerini kendiniz belirleyerek,
hic bir krizden etkilenmeden,
hicbir riske girmeden,
czi yatirimla,
mkemmel kazanclar elde etmek istemezmisiniz ?

Geni bilgi iin: Tel. 0212 - 507 75 02, Faks. 0212 - 507 75 28
start2004 <at> mynet.com

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Bryce as root | 1 Jan 2004 23:43
Picon

2.6.1-rc1 - RAID5 -> oops -> other mischief

Umm
Ok,.. basically scenario is as follows,...
4 300Gb drives
after getting it all up and running we disconnect hdb from the ide chain
curtosey of a hot swap drive bay. The expectation is that the spare disk
will get configured and pulled in (hdd1 in this case)
In fact this is indeed what happens
It's what happens afterwards thats goes horribly wrong. (see appended info)

Advice? (other than "don't do that then")
Is this a kernel bug or an artifact of the unexpected pull of the drive
even though the system wasn't using it at the time.

rebooting the box after the crash seems to show no real ill effects
apart form the expected rebuild on the spare drive

[root <at> ZenIV root]# cat /proc/mdstat 
Personalities : [raid5] 
md0 : active raid5 hdd1[3] hdc1[2] hda1[0]
      585938432 blocks level 5, 128k chunk, algorithm 2 [3/2] [U_U]
      [>....................]  recovery =  0.7% (2333696/292969216) finish=254.7min speed=19011K/sec
unused devices: <none>

and just for the hell of it,.. lets shutdown and reinsert hdb before
the resync is done and see what happens...

[root <at> ZenIV root]# cat /proc/mdstat 
Personalities : [raid5] 
md0 : active raid5 hdc1[2] hdd1[1] hda1[0]
      585938432 blocks level 5, 128k chunk, algorithm 2 [3/3] [UUU]
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rich West | 2 Jan 2004 17:36

Linux RAID - Moving array from one system to another

I'm attempting a full system upgrade and, after a couple of attempts and 
quick back-outs, I figured I would break down and ask.. I was unable to 
find anything via Google regarding this, so here goes:

Scenerio is:
o I have an older server running Linux Software RAID-5 across 5 disks 
that are all housed in an external case (including the root drive which 
is not part of the RAID-5 array)
o The server is running quite happily, but the OS (a RH 6.1 system that 
has been upgraded throught the years to RH 8)  is in need of an upgrade.
o We obtained a 1U Dell with hardware raid which we loaded the OS on the 
root mirror.
o The 1U unit also has an onboard Adaptec SCSI card (outside of the 
megaraid card).
o We want to migrate over to the 1U server

What were were thinking was that we could shutdown the old server, 
disconnect the extrenal SCSI case, plug it in to the new server, and 
boot it with the hopes that the OS would recognize the RAID partition.  
Unfortunately, that did not happen.  It did see the drives, but did not 
autodetect the RAID-5 array.

We tried mdadm --assemble /dev/md0 /dev/sda1 /dev/sdc1 /dev/sdd1 
/dev/sde1 /dev/sdf1.  It appeared to work as we were able to mount the 
drive, but any access to the array resulted in the OS freezing as it 
marked all of the drives as failed.

With the new system, because of the arrangement, the drive letters all 
got re-adjusted compared to the old server.
(Continue reading)

Permalink | Reply | 0 comments |
headers
AndyLiebman | 3 Jan 2004 15:47
Picon
Favicon

Software RAID-5 safe under 2.6 kernel?

Is there any "definitive word" about whether it's safe to use software RAID-5 
under the released version of the 2.6 kernel? I have heard about various 
problems on this list. Are they now resolved? Are there specific configurations to 
watch out for? If anybody has this information, it might be nice to post it. 

Andy Liebman
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 1 comment |
headers
Daniel Brahneborg | 3 Jan 2004 16:11

Re: Software RAID-5 safe under 2.6 kernel?

On Sat, Jan 03, 2004 at 09:47:57AM -0500, AndyLiebman <at> aol.com wrote:
> Is there any "definitive word" about whether it's safe to use software RAID-5 
> under the released version of the 2.6 kernel? I have heard about various 
> problems on this list. Are they now resolved? Are there specific configurations to 
> watch out for? If anybody has this information, it might be nice to post it. 

A definite word for the 2.4 kernel, especially when using SATA,
would also be welcome.

From my own experiences, the SATA chipsets from Silicon Image
and VIA has problems with both RAID1 and RAID5, even though
normal file systems work fine.

/Basic

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Matthew Simpson | 4 Jan 2004 03:39

please help, I've screwed up my RAID 1 install

Hello everyone, I've really buggered up a RAID 1 install, and I need some
help.

My first mistake was when I was setting up the partition tables, the HOWTO I
was reading mentioned to set the partition type to 0xfd in fdisk.  I've
always used 82 and 83 so I assumed that it may be prudent to actually type
0xfd into fdisk instead of just fd... which fdisk promptly accepted as "00"
[empty].  I didn't notice that, though.

I started out originally with the entire disks partitioned this way, and I
could read/write data, but I couldn't boot from /dev/md0 using the boot
floppy I set up.

I then changed it so that I have hda1, hda2, and hda3 [and corresponding
hdc1, hdc2, hdc3].  Hda1/hdc1 are still erroneously marked 0xfd, and are
80GB.  Hda2/hdc2 are marked 83, Hda3/hdc3 are marked 82 [swap].  I'm booting
into hda2 from the floppy, and then I can:

mkraid /dev/md0
mount -text3 /dev/md0 /drives/md0

and it works.

[you can see my /etc/raidtab at the bottom of this message]

The problem is, if I reboot the machine, then I cannot mount /dev/md0 again
until I do a mkraid /dev/md0 --really-force and rewrite the superblock.  I
do not lose any data, but I know this "can't be good" [tm].

What can I do to fix this?  I've tried setting the partition types for
(Continue reading)

Permalink | Reply | 1 comment |
headers
Mike Fedyk | 4 Jan 2004 08:09

Re: please help, I've screwed up my RAID 1 install

On Sat, Jan 03, 2004 at 08:39:15PM -0600, Matthew Simpson wrote:
> The problem is, if I reboot the machine, then I cannot mount /dev/md0 again
> until I do a mkraid /dev/md0 --really-force and rewrite the superblock.  I
> do not lose any data, but I know this "can't be good" [tm].
> 
> What can I do to fix this?  I've tried setting the partition types for
> hda1/hdc1 to the correct "fd" type, but fdisk complains "Partition 1 does
> not exist yet".
> 
> Also, it is possible to boot from a RAID device, is it not?  I assume it
> wasn't working before because of the superblock problem.
> 

Try changing your partitions with cfdisk, and learn and use mdadm for your
raid arrays.  You'll thank me. :-D
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Bin Ren | 5 Jan 2004 12:58
Picon
Picon
Favicon

raid1_conf_t member meanings

Hi,

I'm reading the source codes of RAID1. In file 
'include/linux/raid/raid1.h',
in struct raid1_private_data, there are these members:

unsigned long start_active, start_ready, start_pending, start_future;
int cnt_done, cnt_active, cnt_ready, cnt_pending, cnt_future;

Could anybody tell me the meaning of 'active, ready, pending, future' 
and
'cnt_done'?

Thanks a lot.
Bin

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Bin Ren | 5 Jan 2004 12:58
Picon
Picon
Favicon

some other raid1_conf_t member meanings (Modified by Bin Ren)

Hi,

I'm reading the source codes of RAID1. In file 
'include/linux/raid/raid1.h',
in struct raid1_private_data, there are these members:

int phase;
int window;

Could anybody tell me their meanings?

Thanks a lot.
Bin

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Måns Rullgård | 6 Jan 2004 03:13
Picon
Picon
Favicon

Force RAID1 as clean


Is there a way to forcibly mark a RAID1 as clean?  I know it can be
dangerous, I just don't want to wait for 200GB of scrap to resync.

For some reason, the resync is terribly slow in Linux 2.6.0, only
~1MB/s.  DMA is enabled on all disks and the individual performance of
each disk is normal.  There are no error messages from the kernel.  It
just doesn't seem right.

--

-- 
Måns Rullgård
mru <at> kth.se

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 3 comments |

Gmane