Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an ipSAN that supports 64 3Tb Hard drives. The SAN limits the volume size of each RAID to be 16HDD's Per volume(16+1 for RAID5). I must split my total HDD space in to 4 volumes. I have a Windows 2k8R2 servers that will be connecting to the 4x RAID 5 volumes.

The problem is the software that will be running on the server. only supports one drive letter for its path. I have looked at striping the 4 iSCSI volumes with windows dynamic disk, but it just seems like a disaster waiting to happen.

What is the best way to combined 4 iSCSI volume in to one single file system in windows 2k8R2?

share|improve this question

I would say that even if you could create such a huge volume, this would be a disaster waiting to happen no matter how you create it (think chkdisk times in case something goes wrong).

If your software needs everything under one drive letter, maybe you can get away with mounting sub-volumes as directories under a master volume (and not as a separate drive letter). Also, you can get creative with NTFS junction points to organize your data.

If your data is stored in one huge file, though, I think it's time to re-think the whole strategy, there is no way to make it work reliably with such huge sizes.

64 * 3TB = 192TB, that's dangerously close to NTFS filesystem limits (256TB for both volume size and file size on Windows Server 2012). And on earlier versions of Windows, you can have 16TB files maximum. So, I think you'll need to split into multiple volumes (and many files), and need to plan accordingly.

share|improve this answer
I agree it should not be in a 192TB contiguous volumes. junction points does sound like the right solution. I was going to make junctions in a Folder called C:\data\ then have sub directories of ./LUN0,./LUN1,./LUN2,./LUN3 and put the data with in those volumes. Ideally I would would rather have just C:\data\ then within that have no sub folders so once LUN0 was full it could eat up space on the next LUN. I guess some sort of "transparent Junction/Symbolic link" – Lightly Salted Jan 25 '13 at 1:21

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .