Board index Linux

RedHat 5.1 -> 5.2 vs. "md" software RAID

RedHat 5.1 -> 5.2 vs. "md" software RAID

Post by Tom Klud » Thu, 19 Nov 1998 04:00:00



Hello!

I have a system which has been running RedHat 5.1 quite happily since
the day it was released.  At some point since then it received some
new hard drives which were set up using "md" to be used in a striped
RAID configuration.  All files on the system were simply copied to the
new /dev/md0.

Now, RedHat 5.2 has been released and I would like to upgrade.  My
problem is that I can't seem to get it to do software RAID.  I don't
have the HD space to place my entire system on a single drive,
upgrade, and then copy it back.

Anyone tried this?  Any suggestions?

FWIW, my loadlin startup line looks like:

c:\loadlin\loadlin.exe c:\loadlin\zimage root=/dev/md0      \
    md=0,0,4096,0,/dev/sdb1,/dev/sdc1 mem=128M ro vga=785   \
    video=vesa:ywrap

I have tried using the "md=" option above on the kernel boot line when
starting the RedHat installation but it doesn't seem to work.

Thanks for any help!

BTW, I would prefer if you could respond via email

appreciated.

--
Tom Kludy       |  http://www-personal.engin.umich.edu/~tkludy

--

 
 
 
Top

1. : Weird ">" redirect behavior vs. ">>" redirect behavior

Hopefully, someone has already seen this and knows whats up.

Simple script myscript.sh:

#!/bin/sh
i=1

date
while [ 1 ]; do
   echo "Count - ${i}"
   cat /etc/system
   i=`expr ${i} + 1`
   sleep 5
done

Run it as:

nohup sh myscript.sh > /tmp/myscript.log &

Let it run for a while.  Then run:

grep Count /tmp/myscript.log | wc -l
ls -l /tmp/myscript.log
cat /dev/null /tmp/myscript.log
ls -l /tmp/myscript.log
ls -l /tmp/myscript.log
ls -l /tmp/myscript.log
grep Count /tmp/myscript.log | wc -l

The file size info on my system (Solaris 8) for the /tmp/myscript.log
is zero at first and then goes right back to where it was but a bit
more when the next iteration of the cat command output /etc/system.

Also, the first grep..wc -l command shows how many times the script
has basically looped.  The second grep will show only a couple.  This
shows that the inode is saying the file contains everything is always
did but the grep command is saying it only contains up to some of
point a buffer - maybe the output file descriptor buffer?  I'm
guessing I'm not a programmer

If you change the ">" to a ">>" with your nohup , it works as
expected. The file is zeroed out and the inode info shows it growing
as you would expect it to.

What's the differences between ">" and ">>" that makes this happen?
Running the script with ksh does the same thing.

Looks like a bug to me.

--
........................................................
......... ..- -. .. -..- .-. ..- .-.. . ... ............
.-- .. -. -... .-.. --- .-- ... -.. .-. --- --- .-.. ...

Sean O'Neill

2. PICO says "can't load 32 bytes" then HANGS!

3. Install Linux Redhat 5.2 with other "passwd" and "group" files

4. File Limitations

5. RedHat 5.2, "/boot/System.map" and "/boot/System.map"

6. FreeBSD2.2.x nfs or kernel bug?

7. "umsdos" vs "vfat" vs "looped ext2"

8. How to coordinate/control write()s to a socket?

9. adobe .ps vs .pdf files confusion: problems reading ".ps" documentation on redhat 5.2 linux

10. GETSERVBYNAME()????????????????????"""""""""""""

11. "upgrade" vs. "install" RedHat??

12. """"""""My SoundBlast 16 pnp isn't up yet""""""""""""

13. HPT370 RAID-1 or Software RAID-1, what's "best"?


All times are UTC
Board index