Not quite the same. The Linux kernel has built in RAID as well as LVM. If he's doing RAID1 as it seems then the LVM isn't needed as that's a completely separate monster. I'm thinking it's likely a bad drive that didn't like the restart. On a RedHat9 system He's likely using an EXT3 filesystem which by default has a journal attached which is pretty much the same thing as the DRL. The IO cost of the journal on EXT3 is extremely negligable. At work I have 8 servers with four 600Gig (yes gig) filesystems each. While building one out I did some different tests using ext2 (no journal) and ext3, raid0+1 and raid5. A raid5 system with the journal is an extremely small impact on a 600 Gig system and even a 1.8TB system (we had time to play with disk configurations). In this case the raid is syncing it's mirrors, not fscking the filesystem so the journal/DRL wouldn't do any good at all. If one of the disks in the mirror is having media or other hardware errors it could be trying and failing thought the kernel has been extremely reliable for me to just puke on a bad disk and mark the array degraded. http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Software-RAID-HOWTO.html Robert Thus spake Brian Schwarz (Brian.Schwarz@veritas.com): > Greg, > > Can't help you with the LVM specifics, but I would suggest investigating > functionality called Dirty Region Logging (DRL). I know we have a feature in > the VERITAS Volume Manager that tracks changes at a block level so the > resync can happen much more quickly. Think of it as similar to a transaction > log or Redo log in Oracle. Not sure if LVM has the same type of > functionality. Won't help you this time, but will save you next time. One > trade-off is that it costs you some I/Os to write and clear the log, would > recommend putting the log on a RAID 10 volume. More info on VERITAS Volume > Manager at www.veritas.com/linux. > > Regards, > > -Brian > > > -----Original Message----- > From: Greg Rasberry [mailto:rgreg-r@pacbell.net] > Sent: Friday, May 30, 2003 10:54 AM > To: 'Linux raid mailing list' > Subject: Software RAID level 1 issue > > > I have a RedHat 9.0 server that went down. On re-start the server has > started to come up just fine. It started re-syncing, the first of the raid > partitions, the first one went buy fast, then the second took a day and the > last drive (md2) has been working on the re-sync for four days (it is > fairly large 70 Gig). We are unable to use the server and cannot pull the > data off of it because the drives have not mounted, etc. > > I was wondering if anyone knows if this is normal, and/or how I can get > around this problem. I understand that the re-sync is supposed to happen in > the background? > > I have only been using Linux for about a year and could really use some > help with this, the system has been down for a week. > Thanks in advance for your help. > > R, > Greg > > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html :wq! --------------------------------------------------------------------------- Robert L. Harris | GPG Key ID: E344DA3B @ x-hkp://pgp.mit.edu DISCLAIMER: These are MY OPINIONS ALONE. I speak for no-one else. Diagnosis: witzelsucht IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net IPv4 = robert@mail.rdlg.net http://www.rdlg.net
Attachment:
pgp00042.pgp
Description: PGP signature
