I noticed that existing SMB network IO will halt while a new disk spins up, even if that disk has nothing to do with servicing existing IO requests.
E.g. start a ffmpeg encode session for source and destination media on the SMB network share, wait for other disks to spin down, ffmpeg chugs along, open file explorer and browse around the SMB filesystem, every time you hit a share with disks spun down there will be a delay while the disks will spin up, while the disks are spinning up ffmpeg transcoding halts until the disk is spun up.
Expected behavior is that existing IO is not halted while unrelated disks are spun up that have nothing to do with servicing that IO.
Recommended Comments
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.