Reply to Thread New Thread |
![]() |
#1 |
|
I think there is a small chance I have asked this before, as I have been thinking about it off and on for a while now, but is it possible to convince an OS that two HDDs are in fact one big one? If it is possible, what would the pros and cons be?
I am asking now as it has come up again due to me htpc [running ubuntu] has one drive that is nearly full and the other one is only partially used. I am using XBMC to watch and listen to things and I can easily add another source but that only works well in library mode. When not in library mode you have to navigate folders and having two folders for movies would be a pain when trying to locate things. Alternatively, I might try in putting some of my movie folders on the other drive but link to them from the previous place and see if XBMC is happy with that. I know some programs are happy to accept a short cut as a folder... |
![]() |
![]() |
#2 |
|
|
![]() |
![]() |
#3 |
|
|
![]() |
![]() |
#4 |
|
RAID doesn't seem to have anything that does it, or if it does, its tech speak is a little beyond me at this point in time. JBOD seems ambiguous as it appears to represent two completely different things. However, JBOD has brought me closer to concatenation/spanning which I guess is what I am after. However, even though I know the advantages of doing it, I do not not if there are any known disadvantages. I can see that there might be some drama at the boundaries but can't be sure of that.
Also, would it be possible to combine concatenation and raid? Like if I had 2 x 1 TB HHDs in one "span" could I RAID them so that they are backed up in another 2 x 1 TB HDDs in a "span"? Edit: Also, when I first saw that "fish slapping maniac" link, I thought it might be to some funny guy going on about drugs or some such...completely missed the "la" part... |
![]() |
![]() |
#5 |
|
|
![]() |
![]() |
#6 |
|
|
![]() |
![]() |
#7 |
|
|
![]() |
![]() |
#8 |
|
Raid can be used to make 2 hard drives appear as a single drive.
Using a RAID 0 set, data is divided into discrete blocks and written to each drive in an alternating fashion (called striping), i.e. block 1 to drive 1, block 2 to drive 2, block 3 to drive 1. When using 2 drives this makes a raid volume that is twice the size of the smallest physical drive, and as the data is striped across both drives the read/write performance is almost doubled. The flaws to this approach are that the resultant raid volume has double the chance of catastrophic failure, as a failure in either physical drive will result in the loss of ALL data. Additionally, you would need to copy all of the data off the drives before creating a raid volume, as all data on the drives is lost when the volume is initially created. There is some good info on the Wikipedia page about raid. I would personally recommend against a RAID 0 set, unless you maintain a regular backup of the data. http://en.wikipedia.org/wiki/RAID |
![]() |
![]() |
#9 |
|
|
![]() |
![]() |
#10 |
|
|
![]() |
Reply to Thread New Thread |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|