Christopher (Drashna)

You can lose any number of drives, and any remaining drives will still keep their data in the pool. However, any data that is just on the failed drives will no longer be in the pool. For the most part, it's straight pass through, basically. So you should see performance equal to the underlying disk's performance. Well, it uses normal NTFS volumes, and places the files in hidden "PoolPart.xxxx" folders. As for accessing over the network, you can use the HaneWin NFS Server. Well, as long as we're open, we'll support the software. However, if we closed our doors, the plan basically would be to remove the licensing components from the software and release them. That way, you could use the and there would be no phoning home. Also, even without a license, our software will still work. This applies to the software right now, as is. The pool would go into a semi-read only mode, but you'd still be able to read data from the pool, without any issues. Either. As above, the files are stored in hidden PoolPart folders, so you could access them that way. But ideally, you'd want/need to install StableBit DrivePool. Once it's installed, it will look for pooled drives and automatically rebuild the pool with the available drives. This depends on what you mean. Linux supports Samba/SMB/CIFS (windows file shares), and there are some NFS servers that would work well with linux. So over the network, no issues, at all. You mean like a system case? If so, a rackmount server chassis will probably be your best bet, actually.

First, I'm sorry to hear about that, as that is never a pleasant experience. Try restarting the service. If that doesn't help, check to see if the files show up, and specifically, PoolPart.xxxx folders.

Have you enabled the "do not query more often than" setting in the SMART tab?

Could you open a ticket at https://stablebit.com/Contact

You may want the "CoveFs_SynchronizeDirectoryTimes" Setting. http://wiki.covecube.com/StableBit_DrivePool_2.x_Advanced_Settings#Editing

Do you know what version of StableBit Scanner that you're using, and how the drives are hooked up?

@mayorville It won't necessarily scan right away. You can start a scan by clicking on the "Start". If that doesn't work, double click on one of the drives, and click on the "Start" for that drive specifically.

Unfortunately, no, there really won't be an update on this. Google Team drive is limited on the number of files that can be hosted. And that limits the size. That would be ~10TB normally, or 5TB if duplication is enabled for the provider. Additionally, because it's a shared drive, it's a potential issue too.

No, it doesn't. Well, mostly. If the data is duplicated, and you're reading the data, it will prefer internal over external drives for the reads. But as for what ports that they're on, that doesn't matter. You can move them around with no ill effect.

I'm glad to hear that!

Unfortunately, there isn't a way to get that to happen. The scanning is a slow process that can take roughly 5 hours per TB. That said, there are a few things that may help. Try disabling the throttling settings.: https://stablebit.com/Support/Scanner/2.X/Manual?Section=Throttling Also, there is an advanced setting that will allow StableBit Scanner to scan multiple drives on the same controller at the same time. http://wiki.covecube.com/StableBit_Scanner_Advanced_Settings#Advanced_Settings It's the "maximum concurrent" setting. Try setting that to 0.

I think we pulled it real quick due to an issue, and have a fixed version out. Is this still an issue?

Check both the share permissions, and the NTFS permissions. Also, do you mind posting the name of the folder?

That's really odd, that that happened! That said, I would recommend remeasuring just in case.

Sorry for the delay. Yeah, this is completely harmless and an artifact of how the pool driver works. Basically we don't block LBA address requests, but we do return errors for them. LBA requests are actually requests for a block of data on the drive, rather than a file request.

You want to rebalance the data to be equal between the drives, you want the "Disk Space Equalizer" balancer plugin. It looks like you have some balancer settings enabled, that may be causing issues. Try disabling all of the balancers but the SSD Optimizer, and see if that helps.

The command is to manually set the duplication status on the entire pool, to make sure that it's disabled. From above, it looked like some of the folders had duplication enabled, so a quick way to fix that ... is that command. However, that doesn't remove the duplicates. That requires a duplication pass that will correct that. At the bottom, in the pool organization bar, click on the arrow "^", and see if it has a "reduplicate" option. If it does, then run that, as it will trigger a duplication pass, and should remove all of the duplicates. If that doesn't work, remasure the pool (under Manage Pool).

For this, try the 1171 build, as this may fix the issue. http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.1.2.1171_x64_BETA.exe

It sounds like it's gotten stuck. Try resetting the settings: http://wiki.covecube.com/StableBit_DrivePool_Q2299585B

I don't really have a good suggestion for this, because of how it works. You may be able to do this, though: http://wiki.covecube.com/StableBit_DrivePool_F1655

Ah, glad it was a simple issue

If you just have the SSD Optimizer balancer enabled, then this should be exactly what you see happening. Also, even the default balancers shouldn't really move things around once the files are on the archive drives, until they're too full.

Should be fine to use both, but they work differently. It means it's not available to change, when it's greyed out. Though, that do you mean by blue? It means that it has set it into standby mode, and the disk may be idled that it's not in standby. Standby is a "best guess" at the status, and has issues with correctly querying the state.

HaneWin NFS Server is probably the best option for NFS server on Windows. And it should work with the pool just fine.

I suspect that this is an issue with the SMB client on Linux, or some setting for this. I've used ubuntu for a while and have not had issues with this. Also, is Network I/O Boost enabled for the pool?