Jump to content

jadik

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by jadik

  1. I am attempting to remove a drive from the pool, while running a fully updated Windows Server 2016 Standard installation and StableBit DrivePool v2.2.2.928. My active DrivePool consists of 22x8tb + 2x4tb drives. The drive removal process begins as expected, but after clearing the drive to about 50% of full drive capacity, I am repeatedly presented with the following dialog: "Error Removing Drive: The operation was canceled." and: "Error Removing Drive: (0xC0000056) - A non close operation has been requested of a file object with a delete pending. (This error was returned when either or both the "Force" options were selected in the "Remove Options" dialog... and no items current exist in the Recycle Bin.) Of course, the "Operation was canceled" dialog would be expected if I had actually canceled the operation. However, no such "cancel" action was manually taken. Subsequently, DrivePool begins to "re-balance" content and restore the removed content. Restarting the service, and/or server, fail to rectify this issue. In making multiple attempts to address this issue after reviewing log files, etc, various different "options" have been selected from the "Remove Options" dialog, including: No option selected Force close any open unduplicated files on the drive being removed Force damaged drive removal (unreadable files will be left on the disk) BOTH Force damaged drive removal & Force close any open files The drive has been checked for errors, and no errors have been found. It would seem that removing a drive is an activity of critical importance, second only to adding a drive... so it is quite frustrating to encounter such an issue, especially on a basically virgin patched & updated Windows Server 2016 installation, dedicated explicitly to serving this pooled collection of drives. Please advise.
  2. jadik

    Running out of RAM

    Thanks, Chris, It appears v2.2.2.928 x64 RC solves the memory leak issue & allows for license activation.
  3. jadik

    Running out of RAM

    I can confirm the memory leak issue exists while running the latest DrivePool release v2.2.1.926 on a fully patched Server 2016 Standard, as well as Server v1803 Core. Normal operating circumstances see active RAM usage between 1.9Gb-2.7Gb. However, with DrivePool v2.2.1.926 installed, 8Gb of RAM is fully consumed within 10hrs of operation, and after increasing the system to 16Gb of RAM, complete RAM usage occurred within 18hrs of boot. Immediately following the uninstallation of v2.2.1.926, reboot and installation of v2.1.1.561, server system performance is fully restored and the memory issue is fully resolved. As Roger79 has indicated, discovery of the root cause of the memory leak isn't exactly straightforward, as all attempts to qualify the culprit process (using ProcExp.exe, Poolmon.exe, RAMMap.exe, etc) have proven not to be immediately useful. I'd be find using v2.1.1.561, however, a bug in this version prevents me from activating my license.
×
×
  • Create New...