Jump to content

Nikuk

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by Nikuk

  1. The "$Recycle.Bin" folder is well, what it sounds like.  It's the recycle bin.  And it's setup by Windows on all non-removable disks.

     

    If the contents aren't showing up, it may be that it's for a different user account, or otherwise misconfigured. 

     

    That said, you should be safe to delete this folder (assuming the contents are not needed). 

    Yes, thank. Maybe I've phrased it poorly, but I wanted to make sure that these covefs folders were not something needed by Drivepool.

     

    There are no other users.

    The 500GB of data doesn't show up anywhere.

    There is no folder to delete as I am unable to find it in Windows explorer.

     

    I suppose I could try to chase it down in a Command Prompt... 

  2. v 2.2.0.739 BETA; Win 10 Pro 64bit; SSD Optimizer

     

    I have an 'expected' 182 GB of non duplicated data on my pool, but today I have discovered 522 GB of non duplicated data sitting in a '$Recycle.Bin' on this pool. I certainly don't recall having set it up. I was only able to see the '$recycle.bin' by going into the [Pool Options > Folder Duplication] tree. 

     

    I have double checked the OS Recycle bin, including system files. I have double checked the Drive letters recycle bin / disk cleanup as well.

     

    This pool is built on (5) 6 TB HDD so I checked through each of them and on the HDD that has the most unduplicated data (435 GB) there is a ".covefs" folder which contains a "reparse" folder, none of which report having any size in Windows explorer. There is one other drive with a .covefs > reparse folder tree but the unduplicated data count is massively smaller (50GB).

  3. I'm getting some pretty slow speeds when using clouddrive local disk pointed at drivepool virtual disk.

     

    The drivepool is built on (6) HDD & (3) SSD utilizing SSD optimizer.

     

    The clouddrive is 'built on' the drivepool drive. I'm using a 4th SSD as the local cache drive (nothing else on it)

     

    When writing a large file (23 GB) to the clouddrive (E:) I'm seeing write speeds running in the 30 MB/s range with peaks upto 70 MB/s. This is looking at the Cache drive, E:, and P:... none of them run any higher.

     

     

     

    Any thoughts?

  4. Sorry, let me expand:

    The os drive is an ssd. Then I have a pool of 6 6tb HDDs that would be the archival drives. This pool reports ~200 mbps in crystaldiskinfo as expected.

    I am considering using an ssd setup as a landing zone with ssd optimizer plug in.

    I would need 3 ssd drives to attain ssd r/w speeds and work with 3x dupe, correct?

     

    Then, splitting an ssd into 3 drive letter partitions would defeat the ssd transfer speed goal, correct?

  5. To confirm, and expand upon some thoughts in here:

    I had a passing thought that I could split a 250gb ssd into 3 partitioned drive letters as a landing zone. This would address any files that use 3x dupe. I admit that this would be greatly vulnerable to a single point of failure and so is not the best practice at all.

    The problem is that I'd be splitting that specific sata port's bandwidth in 3 as well.... so instead of 600 mbps I'd probably be back down to 200 mbps after all. Correct?

     

    Also, if I'm primarily writing to the pool via network transfer I wouldn't necessarily see much advantage anyways..? It's on a gigabit LAN but some devices still use 100mb nic's.

×
×
  • Create New...