Azza666

Thanks to everyone who offered suggestions. Someone mention bad paths being stored in memory. I checked all my other dockers and they were fine. so I checked plugins and the appdata backup was referencing a path to a drive which used to be attached (no longer there) via unasssigned devices!

Well I fixed the path error pointed out in a previous post for libresonic. no luck. Now after a day after a reboot I'm at 86% of 32G used. latest diagnostics attached. Once again any help would be very well received vhs-diagnostics-20170227-1832.zip

I've modified the docker setting and will monitor my server closely over the next few days.

I had been using the File Integrity plugin. I removed this earlier following advice from another topic even if is not the plugin mentioned. Just to see if there is impact. thanks for the suggestion anyway.

Got to 100% so had to reboot

df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 128M 3.6M 125M 3% /var/log so it doesn't appear to be out of control logging. I'm not sure what other useful information the diagnostics tell us. at this point I'm still sitting at 86% but would expect to be at 100% before the day is out. her is a full df -h df.txt

Upon further investigation within var there is a bunch of stuff which looks like btrfs volumes. If that expected. Looks like a lot of docker stuff from what I can see. Also looks like var is mounted as part of rootfs.

Thanks for the reply. I've had a good look around these topics. They are either unresolved or they are unrelated to the issue I am experiencing. ive looked at my diagnostics but they don't see anything out of the ordinary. But some of the stuff in there is way over my head

Since the 6.3 beta testing I've had this issues where the rootfs would fill up to 100% At this point that all dockers would crash out and the system is pretty much useless. At this point a diagnostics command fails due to lack of space. The only option I have at this time is to reboot the server. This time I've managed to catch it at 86% please find diagnostics attached. Any help would be appreciated. vhs-diagnostics-20170226-1126.zip

Imho you want your sab to use your cache drives as all of the little files are created and deleted and the downloaded files building before being unrared will mean that parity will be getting written a bucket load. All for transient files.

Worked for me. I'd been having trouble getting this to work. Cheers!

As far as I know xfs_repair does maintain parity

Great stuff!

Did you make sure the config file still has your api key?

I have the same board and I have Iommu enabled. All the appropriate can be found in the bios and can be turned on there. Unless of course you bought the wrong stepping of CPU. One of the early steppingstone of the 2670 v1 don't play well with VT-x and VT-d You may want to flash the latest bios for your motherboard.