Jump to content
Division-M Community

esac

Members
  • Content Count

    10
  • Joined

  • Last visited

  1. Every once in a while when I reboot, the system comes back up and services such as Dropbox, Media Center, and Windows Live Mesh think that the E drive (the DB drive) has disappeared, so it disassociates with the drive, and I have to reset everything back up.
  2. Thanks, would love to see this enabled!
  3. Definitely understood, that may be it. An alternative I can think of would be to keep the GUID as the Volume Label, or even a text file on the root of the drive?
  4. Thanks, but I already know what RAID is and all of the various levels. What I am asking for is that when you have files duplicated between 2 drives, DriveBender has an underlying mechanism to read those files. If a read comes in for a file on DriveA, DriveBender can immediately read the next block off DriveB and store it in memory so that the data is immediately available in anticipation of that next read. Granted, that read may not come, but it would be as simple as flushing that cache based on age or maximum memory.
  5. Hate to say it, but a ton of misinformation here as well. Windows does have a file system cache. Typically this is enough so that if you are accessing the file within a short time frame (temporal locality), then it will utilize that cache. It is an in memory cache, and is actually rather small. It has nothing to do with 'swap files' or as windows calls it 'paging files'. In fact, paging files are used as a backing store for code and data that resides in memory, so that when there is a demand for memory that is higher than what the system has, it can satisfy that from disk instead. Paging is actually BAD in most sense of the word (better than running out of memory, but still you would rather get that code/data from memory rather than disk). In fact, what you are saying makes no sense, that instead of going to disk, it will ... uhm ... go to disk??? Anyway, even if that all made sense (it doesn't), then that solves nothing for writes. Windows can not cache data it doesn't know about which is what happens when you write a file. Finally, as i've pointed out before, Drive Bender is already architected to take disk space into account. What do you think happens when you have a 1TB and a 2TB drive in the same pool? Eventually, 1TB will be used up, and all subsequent files will go to the 2TB drive. This scenario makes no difference. Writing to an SSD drive makes a HUGE performance improvement and I think this functionality will set DriveBender apart from competing products.
  6. Wow, so much misinformation here. 1. Who said I was copying across the network. 2. Even if it was across the network, disk transfer rates for a 7200 RPM fall within the 100 megaBYTE range for sequential reads and writes (800 megabit) with no other disk activity occuring, so still not enough to saturate the gigabit (admittedly it does get close, but again this is with no other disk activity). Random reads and writes do not even come CLOSE to saturation. 3. If you were copying 50GB of files onto your server, DriveBender is already smart enough to know where to place a file if it is too big for the destination pool drive, so it might write the first 20GB to the SSD, and then future writes would go to the larger drive. 4. Not everybody here runs WHS (which is a poor assumption on your part). I run Windows 7 Ultimate with Media Center, streaming to 3 XBOX 360's throughout the day, backing up 4 laptops worth of data via Windows Live Mesh (bunch of small file reads and writes), and uploading that all to Crashplan. It also acts as a file and print server, although not as much. 5. All of my other computers do have SSD's, but even if they didn't, 30GB is not really enough to even put an operating system on nowadays, so unless the system had SRT, I wouldn't even consider it (and even then as i've had issues with SRT).
  7. I have 2 drives, p:\ and q:\ in a pool. I don't like how drive bender stores everything in p:\{guid}. Why can't it just be moved to the root of the drive directly?
  8. For duplicated files, would like the ability for the reads to stripe across both drives, so 2 separate reads on 2 separate drives.
  9. I have a spare 30 GB SSD lying around. Not enough to really put any data on, but would love it if DriveBender can use it as a cache. Keep the most recently used files on it for reading, and all writes go to the SSD, and then get moved on periods of low disk activity to the larger pool.
  10. When I first setup my pool as follows DB1 - 1.8 TB Volume (Master Node) DB2 - 475GB Volume DB3 - 475GB Volume After rebooting today, I noticed that DB2 is now the Master Node. I have no idea what that means, or if it is important. If it is important, why did it change? Thanks!
×
×
  • Create New...