macmanluke

Hello Looking to upgrade shortly to 6.9 and do the SSD fix - cache ssd pool has written 190TB in a year... In the instructions i noticed it says use mover to transfer cache to array but onto a btrfs drive - is there any reason for this? my array is XFS If its required is there any way of converting a drive without messing up the array/parity etc? Currently have one drive thats empty (and excluded from shares globally) as i moved its contents off when i had a drive start failing recently (since replaced/rebuilt array) thanks!

Just set this up and have a strange issue If i use lancache im getting sub 2MB/s downloads in battle.net launcher but if i bypass it i get my usual 15-20MB/s Any suggestions? quick test in steam does not seem to have the same issues thanks! edit: looks like its recommended to change the slice size for blizzard - where is the config files for this docker?

anyone having issues with the log file growing for this docker?

I wonder if the software trying to get WU very often is also causing issues as if i leave it running i get nothing but if i stop it overnight ill get a new WU straight away when restarted

Installed it yesterday and it was working fine all day Today i noticed it was doing nothing Searching the logs i see: Its just repeating that, got it to do something restarting the docker but was soon doing nothing again Is there something wrong (or actually just nothing for it to do?

Iv had issues since the last update, crashing/growing to 4gb! had to do a force upgrade to get it to work again, see how it goes.... edit: nup crashes almost straight after booting

Just noticed i have same issue Tried -i br0 but still pegging 1 core

Just noticed i have same issue Trying -i br0 now see how i go, wondered why i had so much cpu usage with nothing much happening Edit: still pegging one core...

Although when i added it to my array its now clearing it again?

my 3TB just finished and succeeded!

just a 3TB but it errored last 2 tries

that worked for me (as a test) will run the whole drive now

I just got the same error pre clearing a Seagate ST3000DM001