Gilboa Davara wrote: I'm not the OP, but one possible reason is to preserve the ability to add additional drives later. My music collection originally lived on a set of RAID-1 devices on two drives, then RAID-5 on three drives, and now RAID-5 on four drives. Only enough free space to copy *one* of the md devices is required. Using LVM to create a single virtual device out of the md devices may make sense, *if* you trust pvmove, which the LVM HOWTO claims doesn't work. -- ======================================================================== Ian Pilcher i.pilcher(a)comcast.net ========================================================================

Gilboa Davara wrote: As I've learned to my sorrow, no amount of RAID will protect you against a misplaced 'rm -rf'. I would love to have a *real* backup of my music collection. Unfortunately, by "real" I mean some sort of relatively stable media that can be put in a safe deposit box or something -- i.e. a USB disk drive is out. To the extent that I've looked, tape solutions are just too damn expensive. -- ======================================================================== Ian Pilcher i.pilcher(a)comcast.net ========================================================================

On Sat, 2006-04-01 at 10:18, Ian Pilcher wrote: Why? Ipods are pretty sturdy things and a laptop drive in a usb case is approximately the same - or a full size drive if you need over a hundred gigs. The trick is to have more than one and rotate them so you don't lose the data at the end of their expected several year life. If it isn't too big, a dvd writer might be a solution. My preference is to have another machine on the network running backuppc (http://backuppc.sourceforge.net/) so there is always an on-line copy with at least a week of history in case you accidentally delete something. Then I periodically raid-mirror that to an external drive that is rotated offsite. -- Les Mikesell lesmikesell(a)gmail.com

On Sat, 1 Apr 2006, Ian Pilcher wrote: It should take 24 dual layer disks. Regardless, the correct way to look at it is "if my hard drive died tomorrow, would it be worth the time and money to me for 50 recordable DVDs to recover?" If the answer is yes - start burning them now and store them somewhere safe. There are more convienent solutions like backuppc or g4l, but it depends entirely on _how much_ the data on the drive is worth to you vs how much money you want to trade for convienent solutions. Personally, I have a complete set of automated 8x daily, 5x weekly, 4x monthly, 3x quarterly and 2x semiannual backups for my personal data in Linux made nightly by a script using rsync over ssh as well as an external 'OneTouch' USB drive I use for my WinXP backups (I don't boot windows very often, so I just back it up manually). I like my data. -- Benjamin Franz If you can't handle reality, it *will* handle you.

When I try to install realplayer in FC5 I get this: [root@localhost Desktop]# ./Real* ./RealPlayer10GOLD(2).bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory Any idea what is wrong Chris

I appreciate what everyone is saying. For our purposes this is the necessary way to go. Does anyone have a suggestion as to how to work around this issue? Does anyone have a direction to point me? TIA Mark Yarbrough _____ From: fedora-list-bounces(a)redhat.com [mailto:fedora-list-bounces@redhat.com] On Behalf Of Mark Yarbrough Sent: Friday, March 31, 2006 10:50 AM To: fedora-list(a)redhat.com Subject: Software Raid 5 (FC5) During install time I was made 10 raid partitions across 5 500GB SATA drives. The final partition /dev/md8 wouldn't partition format and anaconda would crash telling me that the partition couldn't be formatted, and required a reboot. After the 3rd attempt I figured that the partitions are all the same size so I will just format it when I am in the running operating system. I took a look at my partitions using fdisk (take note that all 5 are the same save the drive number it self) <see paste at bottom> The partitions are there. /dev/sdX11 is the partition that I am trying to use. I tried to make the raid partitions to no avail. I looked at /etc/mdadm.conf and saw that /dev/md8 is there. From my limited understanding I am under the assumption that the raid is made and all I need to do is format it. I try to format it and I get the error reporting the device size to be zero. The partitions are clearly not zero. I am now stuck. What should I do next? Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 28683 230396166 fd Linux raid autodetect /dev/sda2 28684 38882 81923467+ fd Linux raid autodetect /dev/sda3 38883 41432 20482875 fd Linux raid autodetect /dev/sda4 41433 60801 155581492+ 5 Extended /dev/sda5 41433 43344 15358108+ fd Linux raid autodetect /dev/sda6 43345 45256 15358108+ fd Linux raid autodetect /dev/sda7 45257 46658 11261533+ fd Linux raid autodetect /dev/sda8 46659 47933 10241406 fd Linux raid autodetect /dev/sda9 47934 49208 10241406 fd Linux raid autodetect /dev/sda10 49209 49845 5116671 fd Linux raid autodetect /dev/sda11 49846 60796 87963876 fd Linux raid autodetect Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 28683 230396166 fd Linux raid autodetect /dev/sdb2 28684 38882 81923467+ fd Linux raid autodetect /dev/sdb3 38883 41432 20482875 fd Linux raid autodetect /dev/sdb4 41433 60801 155581492+ 5 Extended /dev/sdb5 41433 43344 15358108+ fd Linux raid autodetect /dev/sdb6 43345 45256 15358108+ fd Linux raid autodetect /dev/sdb7 45257 46658 11261533+ fd Linux raid autodetect /dev/sdb8 46659 47933 10241406 fd Linux raid autodetect /dev/sdb9 47934 49208 10241406 fd Linux raid autodetect /dev/sdb10 49209 49845 5116671 fd Linux raid autodetect /dev/sdb11 49846 60796 87963876 fd Linux raid autodetect Disk /dev/sdc: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 * 1 28683 230396166 fd Linux raid autodetect /dev/sdc2 28684 38882 81923467+ fd Linux raid autodetect /dev/sdc3 38883 41432 20482875 fd Linux raid autodetect /dev/sdc4 41433 60801 155581492+ 5 Extended /dev/sdc5 41433 43344 15358108+ fd Linux raid autodetect /dev/sdc6 43345 45256 15358108+ fd Linux raid autodetect /dev/sdc7 45257 46658 11261533+ fd Linux raid autodetect /dev/sdc8 46659 47933 10241406 fd Linux raid autodetect /dev/sdc9 47934 49208 10241406 fd Linux raid autodetect /dev/sdc10 49209 49845 5116671 fd Linux raid autodetect /dev/sdc11 49846 60796 87963876 fd Linux raid autodetect Disk /dev/sdd: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdd1 * 1 28683 230396166 fd Linux raid autodetect /dev/sdd2 28684 38882 81923467+ fd Linux raid autodetect /dev/sdd3 38883 41432 20482875 fd Linux raid autodetect /dev/sdd4 41433 60801 155581492+ 5 Extended /dev/sdd5 41433 43344 15358108+ fd Linux raid autodetect /dev/sdd6 43345 45256 15358108+ fd Linux raid autodetect /dev/sdd7 45257 46658 11261533+ fd Linux raid autodetect /dev/sdd8 46659 47933 10241406 fd Linux raid autodetect /dev/sdd9 47934 49208 10241406 fd Linux raid autodetect /dev/sdd10 49209 49845 5116671 fd Linux raid autodetect /dev/sdd11 49846 60796 87963876 fd Linux raid autodetect Disk /dev/sde: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sde1 * 1 28683 230396166 fd Linux raid autodetect /dev/sde2 28684 38882 81923467+ fd Linux raid autodetect /dev/sde3 38883 41432 20482875 fd Linux raid autodetect /dev/sde4 41433 60801 155581492+ 5 Extended /dev/sde5 41433 43344 15358108+ fd Linux raid autodetect /dev/sde6 43345 45256 15358108+ fd Linux raid autodetect /dev/sde7 45257 46658 11261533+ fd Linux raid autodetect /dev/sde8 46659 47933 10241406 fd Linux raid autodetect /dev/sde9 47934 49208 10241406 fd Linux raid autodetect /dev/sde10 49209 49845 5116671 fd Linux raid autodetect /dev/sde11 49846 60796 87963876 fd Linux raid autodetect # mdadm.conf written out by anaconda DEVICE partitions MAILADDR root ARRAY /dev/md8 level=raid5 num-devices=5 uuid=fc489661:c7e54273:f9a60c82:fb747b29 ARRAY /dev/md6 level=raid5 num-devices=5 uuid=eac1a77f:5278bfcd:4ae75c92:7ecde09b ARRAY /dev/md3 level=raid5 num-devices=5 uuid=1e94cb1d:f84f5a3b:1e0ff333:408d5bb7 ARRAY /dev/md5 level=raid5 num-devices=5 uuid=f5bfaf8b:8a591cf0:d73b7d31:4c07a93b ARRAY /dev/md1 level=raid5 num-devices=5 uuid=0bf1a445:323d5326:5a7a92fc:1c346c33 ARRAY /dev/md9 level=raid5 num-devices=5 uuid=f5811eae:cfb21182:41881dcf:739f1bad ARRAY /dev/md4 level=raid5 num-devices=5 uuid=348c95b9:df7feee6:41713309:a9324496 ARRAY /dev/md0 level=raid5 num-devices=5 uuid=bf7ef721:318d6d4e:b626b349:5f9c7e15 ARRAY /dev/md7 level=raid5 num-devices=5 uuid=a196ca52:c6700579:ff5a0379:9d6c9084 ARRAY /dev/md2 level=raid5 num-devices=5 uuid=5e0d3003:e65e36d0:25158ed3:f81e126d