-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Greyhole slow when transferring things via Radarr/Sonarr etc. #302
Comments
It seems that copying anything from a non-greyhole/samba share into a greyhole/samba share causes the slowdowns. Currently we're looking at around 1-5kb/s average throughput rate. I have reinstalled Greyhole, removed mysql, and replaced it with MariaDB (far lower resource usage too), and I've also reinstalled Samba, same issues unfortunately. |
No much Greyhole-related is used, when copying files onto a share : Samba handles this by itself, and will log some data for the Greyhole daemon to work with, once the file is finished being written to. Some Samba version will log a "lot" of "write" logs, and this is why those logs are stored in Also : did you try to just comment out, temporarily, the |
File is going from Without vfs objects (and restarted GH + Samba)
Looks like the spool folder is barely being used in this particular case: And GH logs seem to be acceptable:
Samba config is pretty generic: https://paste.modem7.com/ZrSl8AyXLB Syslog: https://paste.modem7.com/44rCXnXodM 20221004010055.mp4 |
Heya,
I've just upgraded from Ubuntu 20.04 to 22.04, and things have gone absolutely awfully slow.
Unsure if this was due to the upgrade in Samba etc.
To start with, what would be the best way of fully wiping Greyhole (including removing the DB), and starting fresh?
I suspect my setup has been running for quite a while with quite a few changes, so a fresh install (backing up greyhole.conf and smb.conf obviously) would probably be a good starting place (especially as the DB may be quite large/unoptimised).
That way I can also do the VFS things as well.
The text was updated successfully, but these errors were encountered: