| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | To RAID or not to RAID? |
-=> Angus Mcleod wrote to All <=-
AM> Here's a thought for my Music Server machine:
AM> Do I actually want to configure the drives as a RAID array? Or do I
AM> simply have two partitions and periodically snapshot/copy one to the
AM> other? Thing is, I won't be _eriting_ to the array that often. I
AM> might be _reading_ data off the array all day as I listen to music, but
AM> I won't be _writing_ to the array other than when I acquire a new
AM> album, which certainly isn't every/all day.
AM> So is there any advantage to configuring two separate partitions and
AM> adding a copy to partition #2 as part of the usual rip/encode/dbinsert
AM> process? I'm thinking you could spin down one disk and run only one
AM> and at some time you could spin up the second disk, unmount/mount and
AM> spin down the first disk so as to spread the wear'n'tear. Make the
AM> changeover a cron-job at 5:30 AM, & maybe an MD5 comparison of all disk
AM> objects so as to spot any differences that need to be eliminated.
AM> Or should I use plain old RAID?
Im interested in how your going to do this as well as upon my return to the
states I am
moving my mp3 drive to a dedicated machine and want to put as least ammount of
wear and tear
on it as possible =)
Arthur Stark / astark{at}tdmonline.com
WWW: tdmonline.com / floydfreaks.com
BBS: tdmonline.org (telnet, ftp, http)
currently listening to Eric Clapton - Singles - - Wonderful Tonight
... Heisenberg may have slept here.
--- MultiMail/Win32 v0.46
þ Synchronet þ Top's Diamond Mine Online - tdmonline.org
* Origin: Joe's Computer & BBS -=joesbbs.com=- (1:275/312)SEEN-BY: 633/267 270 @PATH: 275/312 396/45 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.