Jump to content

jmone

Members
  • Posts

    163
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by jmone

  1. jmone

    REFS in pool

    FYI - I also found: - When Reformatting CheckSum is set back to None (need to reenable it) - CHECKSUM_TYPE_CRC64 is used when formated as 64K Sectors - CHECKSUM_TYPE_CRC32 is used when formated as 4K Sectors
  2. jmone

    REFS in pool

    From what I could find on ReFS features there seems to be a new Fast/Block cloning added post V1 that may be on interest for DrivePool: https://blog.workinghardinit.work/2016/08/25/veeam-leads-the-way-by-leveraging-refs-v3-capabilities/ I've got a couple of 8TB Hitachi coming so I'll probably do a rolling ReFS upgrade of the Seagate 8TBs
  3. OS: Win 10 Pro - 64Bit - V1703 - Build 15063.448 Anti Virus: Windows Defender (std settings) DrivePool: No Data Duplicated, Ordered File Placement Balancer, File Placement Rules Will run a memtest and report back. Did the mini dump show anything? Thanks Nathan
  4. V767 looks pretty good (I like the addition of the ReFS drives) but I'm having an issue when trying to remove a Drive. I've tried a couple of time to remove a drive but both times got a BSOD with a APC Index Mismatch. I'm now moving the files manually with the DriveServer service stopped between drives and the only thing I can see is I have some directories with Full Stops in them that Windows does not like, but I'm not sure if this is the issue. Windows did create Mini Dumps (Attached). Thanks Nathan MiniDumps.zip
  5. jmone

    REFS in pool

    Thanks - I use you script for this! I'm pondering if I should reformat to V3.2 for all the drives on this pool for consistency but it will take some time to copy off and back all the data.
  6. jmone

    REFS in pool

    Found this article - https://blog.workinghardinit.work/tag/refs-versions/and I can confirm that fsutil does work! I have drives that are ReFS V1.2 and now with Win10 ReFS V3.2. Also tells you if you have Check Sum set You can also run it on mount points without a Drive Letter as follows (the first drive listed is the new one I added to the pool - need to set CheckSum!) C:\Users\natha>fsutil fsinfo refsinfo C:\Users\natha\Desktop\MountPoints\045f6 REFS Volume Serial Number : 0x52e2b127e2b10fe9 REFS Version : 3.2 Number Sectors : 0x00000003a37c0000 Total Clusters : 0x000000000746f800 Free Clusters : 0x0000000003b57bc0 Total Reserved : 0x0000000000077c04 Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 65536 Checksum Type: CHECKSUM_TYPE_NONE C:\Users\natha>fsutil fsinfo refsinfo C:\Users\natha\Desktop\MountPoints\416c0 REFS Volume Serial Number : 0x28d095dfd095b392 REFS Version : 1.2 Number Sectors : 0x00000001d1c00000 Total Clusters : 0x0000000003a38000 Free Clusters : 0x0000000001495578 Total Reserved : 0x0000000000000000 Bytes Per Sector : 512 Bytes Per Physical Sector : 4096 Bytes Per Cluster : 65536 Checksum Type: CHECKSUM_TYPE_CRC64
  7. jmone

    REFS in pool

    OK - I've pushed ahead and formatted one ReFS drive formatted using Windows 10 Creator Update and it is working fine in the pool so far. I know about the backwards compatibility but I'm not worried on that as I would reformat drives if moving between systems anyway (and I'm sure that at some point WS2016 will support the newer version). I'm still unclear of what the different is between the ReFS versions however and if their is a way of updating the older ReFS file system to the newer one without a reformat (as this will take a long time of 8TB drives to move data on and back on if you have to reformat). I'm also unclear on how to tell what version of ReFS the drive has been formatted with.
  8. jmone

    REFS in pool

    Any issues with mixing the ReFS versions (eg WS2012R2 vs Win10) in a pool on Win10? The disks that I'm using on my Win10 pool were originally formatted on a WS2012R2 box or with the nasty Windows 10 Reg hack. I know that any disk I format on Win10 is a "newer" version of ReFS and will not be recognised (for now) on WS2012R2 but apart from that any issues? Thanks Nathan
  9. Thing was I had it set in DP to be 99% Full / 1GB Free and the drives filled up.... Like to 100%. One had a only few KB free then after a balance had 0 (I ended up with 3 drives with 0 free). Anyway, I've now set it to 98% / 2GB Free and the lowest is 1GB free (rest are 1.5 to - 2GB free).
  10. So deleted some content from my pool (that made some space of my three full drives), and I could the update the ownership and permissions. I have the following now set (does this look OK)? Owner - Administrators Permission Entries (all Inherited from "M:\") - Administrators (Full Control) - System (Full Control) - Authenticated Users (Modify) - Users (Read & Execute) I then have selected sub directories set up as a network share
  11. I'm trying to clean up my permissions but I'm getting an issue where Windows is Complaining I don't have enough Disk Space. In Drive Pool, I'm using "Ordered File Placement" and had the Limit set to 99% Full / 1GB Free. Looking at some of these drive in DP some have around 1GB free, but 3 are not reporting any Free Space stats at all. I tried to change the Limit set to 98% / 2GB Free and did a re balance but nothing moved. Any Suggestions? Thanks Nathan
  12. Good news on ReFS Support!... I love this format for my pools, with 0 issues to date. It will be interesting to see when/if the Server Line gets the same ReFS version support as Windows 10 (esp as it has been out for a couple of months) and what all the V1/2/3 differences are. I can not find any comparison table but only this presentation on V2 http://www.snia.org/sites/default/files/SDC15_presentations/file_sys/JRTipton_ReFS_v2.pdf
  13. I "presume" Server 2016 uses the newer ReFS version (I've seen reports saying V2 and V3 so no idea what is "correct" and what the differences are).
  14. So ReFS is now an native format option in Windows 10 (from build 15042). I'm not sure however if it is ReFS v1, v2, v3 (or some other difference) as drives I format as ReFS in Win 10 can not be read in Win Sever 2012R2, they appear as RAW (but as always, those formatted in 2012R2 can be read in Win10). I can not find out much on the details of the new ReFS in Win 10 option, but it is good it has gone main stream!
  15. ...and I STILL have to do this after adding a new disk.
  16. Thanks - It's all done and working fine. I'll be doing more swaps soonish as I upgrade another 4tb drive to 8tb. I don't use duplication on the pool (I have another pool on another server that a use to Backup this pool from). FYI my use case is pretty simple: - For BD Rips use the 8TB Seagate Archive Drives and fill them up one at a time and in order - For other items (video editing, VM images, prog files etc) use the 4TB Hitachi 7200 drives - I've even turned off the SSD option - Once or week or so I do a compare with the 2nd backup pool on the other server (using FreeFileSync) before committing any changes to this pool (in case of accidental deletes etc).
  17. At first I used the remove button but it failed with a msg about no avail disk space after it filled up some free space from one of the other drives and did not put anything on the new 8TB HDD in the pool. So after reading some posts I'm using the Balancer. I've only 300GB to go so I'll let it run (+ I'm now away with work for a few days). When I'm back I'll then "remove" the hopefully empty drive and reset the Balancer to they way it was.
  18. Fast is anything approaching raw disk copy speed, and I think DrivePool does a pretty good job of approaching this when reading / writing to the pool for foreground processes. When copy large files (It is worth noting that the raw speed difference is considerable between large and small files and physical placement on the platters, type and mix of HDD etc) between my pools I can hit 130MB/sec but on average I would say I get 90MB/Sec on mixed files, or about 315GB per hour (this is between two Hitachi 4TB 7,200rpm drives I've set as SSD on each pool). According to Drashna the Balancing Engine uses background processes and he states that takes "longer" than what you can get if you stop the DrivePool process and copy the files manually. I certainly see this on my system as it currently moving the large (multi GB) files at around 45MB/Sec or about 160GB per hour, and an average closer to 35MB/Sec or about 125GB per hour on mixed files.... so about half the throughput at best (note: this is also copying from a Hitachi to a Seagate 8TB Archive which are slower on sustained writes which complicates the comparison!!)
  19. Some Feedback on the Drive Add / Remove / Swap use case for me. As my Pool Fills up, I remove the oldest drive (say 4TB) and replace with a bigger drive (say 8TB) due to lack of ports on one of my Pools. In DriveBender you could 'swap drives' and it was nice and fast. DrivePool on the other hand uses the Balancer which is slow and tends to first move the files to your SSD (if you have one) not the new drive (which then filled it up and the process stopped). I've been reading and playing with a few of the settings and work arounds but it all takes a long time and is harder than it should be. I just want to swap the drives as fast as possible then let the balancer do its thing over time. Looking forward to when the dev of this part makes this part work. Thanks Nathan
  20. Odd one. I did some WSE2012R2 Maintenance (Oct rollup patches) and added a new drive to the pool. I noticed that the Users and Devices in the WSE Dashboad were blank when run on the server I I could not Sign In from a PC at all. On checking, the WSE Mgt Services was not running. I could start it but it would stop again. Tried the C:\ProgramData\Microsoft\Windows Server\Data\DevicesInfo.bak --> C:\ProgramData\Microsoft\Windows Server\Data\DevicesInfo.xml but that did not work. In the end I had to do a "run wbadmin delete catalog" and then resetup the Server Backup from the Dashboard. Seems OK again. Thanks Nathan
  21. Odd one.... I lost write access to my pool so fired up the Drive Pool GUI and had a single screen asking to "Transfer Licence to this PC" which I did, and then my pool was all good. No idea what caused Drive Pool to think I had a new PC / HW though I had been playing with some OC settings and had a Win 10 BSOD / repair check as a result, but that is the only thing I could think of. Running 2.2.0.682 Beta Thanks Nathan
  22. Got your 10GBe yet? All working well for me
  23. I have a bunch of the 8TB Seagates in 2 x 40TB Pools that hold my BD Rips - Works great (I have 4TB Hitachi as my "landing drives").
×
×
  • Create New...