Ka Lam

This is still an issue for me.

so I tried the auto-tuning level, on the Win11 machine, it doesn't help.

No. I never got to the bottom of it, so I still observe the issue. A few new things I observed are: 1) Win11 OS as SMB client still has the same latency issue. (I built a new desktop, new CPU/MB + fresh install OS) 2) (Window's) scp to/from the pool drive has no latency issue. 3) I also has another (new to me) desktop, which has a new SSD, fresh installed Win10 OS, using a USB-wifi connection, observe the same latency issue. I already has "Network I/O Boost" option turned on at the pool. I will give auto-tuning level a try next time I have a chance. It's likely that it will be 7 to 10 days before I can try it tho.

Current environment description: Host that has DrivePool installed OS is Win10 Pro 64bit. DrivePool version 2.2.4.1162. Client OS is also Win10 Pro 64bit. Both are connected via 1G wired Ethernet by a switch. The issue: I have shared out some directory from a pool from the host. I've always noticed access delay issue, but have worked around the problem for years (> 3, if not 5 years. The systems back then was running Win 7) Recently I spend some effort to try to dig into the problem a bit, and here is what I find so far: On the host, on a drive (t:) that's part of the pool (e:), I create an exact copy of a sub-dir that's part of the pool. i.e. E:/Drivepool/TestSubject1 has the same content as T:/TestSubject2 (size of the sub-dir is around 2.?? GB) The copy on the host from TestSubject1 to TestSubject2 is "fast" (in the expected 100MB/s range, and the copy start as soon as I drag and drop) I also share out the TestSubject2 as SMB share. On the client, I open separate file explore windows to each of the SMB share of the host. And drag and drop copy from the SMB share TestSubject1 and TestSubject2 to a client local HDD. The copy from TestSubject1 took 30+ seconds to get start, but once it start, the speed is "normal" (80-90MB/s) The copy from TestSubject2 started right the way (no 30 seconds pause), and the speed is in the same range (80-90MB/s) I also have a RDP window open from the client to the host, and I can observe the DrivePool Windows (where I can see the "Disk activity") During the 30 sec pause, there is no disk activity on the pool, once the copying start (as observed in the copy progress dialog box), then DrivePool windows show activity. I have search this forums, and noticed a few possibly related posts https://community.covecube.com/index.php?/topic/3984-pauses-in-file-operations-on-shares-caused-by-drivepool/ and some previous suggestions: https://wiki.covecube.com/StableBit_DrivePool_Q542215 (I have done this on the host to disable Windows Search indexing) https://wiki.covecube.com/StableBit_DrivePool_Q7420208 (I didn't do this, as I don't see how this would apply.) Background: I start digging into this issue because I have a VM running dietpi (OS) running Plex Server, accessing a music folder via SAMBA to the host (same host as above). When Plex is scanning the music folder, it took forever (as in many days) and I noticed (by netdata) there is high iowait. Eventually, I gave up and stop using the SAMBA to access to host, and just make a complete copy of all my music file into the VM that's running, and let Plex re-scan it. And I notice the night and day different! The same Plex VM also access via SAMBA to my video folder, and it always takes a while (30 sec ish? :P) to start stream my video, but it has no problem streaming content in 1080p or 4k (thus transfer bandwidth is not a problem.) Which lead me to think, it's a latency issue (takes a long while to start, once it started, it's 'fast') I always feels that something is "wrong", but until the above Plex music folder experience, I couldn't pinpoint what's wrong. I also though it's that host, but given I did a re-install of the OS (when I upgraded from Win7 to Win10) and it didn't make a difference. Then the idea of trying the SMB share on a non-pool drive was tested, and that was 'fast' (latency), then I suspect it has something to do with Drivepool (thus this post). Further background: My drive pool currently has 1x14TB, 3x8TB, 2x4TB HDD, files are mostly 2x duplicated, some sub-folders are 3x duplicated. The pool has evolved over time, from 4x2TB to mostly 4TB to the current state. I also use Windows Performance Monitor to observe the host and the client, I got the idea from this webpage from Microsoft. On the host, I observed "SMB Server" and "SMB Server Sessions" (about Read Bytes/sec, Read Request/Sec, Avg. Read Queue Length, Current Data Queue Length, Current Open File Count, Current Pending Requests...etc). On the client, I observed "SMB Client Shares" for both TestSubject1 and TestSubject2 (independently) (about Avg Bytes/Read, Avg Data Queue Length, Avg Read Queue Length, Avg. sec/Data Request, Avg. sec/Read, Current Data Queue Length,...etc) The observation is, during the 'pause', the client side counter has no activity, after the 'pause' (ie, file copy has started), the performance counter of TestSubject1 and TestSubject2's activities are "comparable". On the host side, the performance counter of SMB Server / Server Sessions are also "no activity" during the pause (but has Data Queue Length of 1) and "normal" looking activity during the actual copy operation. (of both copy) If extra details/log/debug trace, or video capture of my above debug action is needed, I can provide them. (I work in the field of computer and is quite technical, and I am willing to work with someone to figure this out.)

Running on Win 7 pro, I have 2 pools defined, big-pool with many physical HDs, another small-pool with 2 x 2TB HDs (it's config for duplication) Stablebit warn me one of the 2TB has a file system damages, so I remove it from the small-pool, and reformat the disk with NTFS, then add it back to small-pool. Fast forward a week or two, I notice something is weird, and it turns out, now I have 3 pools. big-pool (e:), small-pool (f:) with one of the 2TB and another pool (g:)with the "once removed, then added 2TB". This is where I need help. g: is not readable, in Computer Management console, disk management, it's marked as Unknown (not initialized), the drivepool UI would keep hanging when I try to run it. What I want to do: get it back to big-pool, small-pool. As far as I can tell, big-pool is "ok", (and it's important it stays ok.) small-pool (f: seems ok.) so I am ok with just blowing away g:, and whatever the content in the 2TB behind it, and re-add them all back to small-pool. But I have no idea how to do that "correctly". The Drivepool UI doesn't have a remove pool. when I look into device manager, under Disk Drives, I see 3 Covecube Virtual Disk, 2 of them just say "Covecube Virtual Disk", the 3rd one say "Covecube Virtual Disk ({cc1dca32-6002-43d9.......})" Please let me know if I need to collect any log to help debug this. Thanks.