OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!

mdgm wrote:
That python release is from last year, as is the version of unrar you have installed. Not sure about par2 bit I think that's old as well.

Par2 simply hasn't been updated since 0.4. For unrar, I pulled the latest from testing, it's now on 1:5.0.10-1. Python 2 hasn't been updated past 2.7.3-4 and quite frankly I'm not familiar enough with python to fix issues in the software I want to run if I upgrade to v3. Also, while older versions of packages may contribute a small amount to the problem, they cannot be the sole cause, since a simple FTP or SMB copy to the device results in the same performance issues whenever the btrfs processes wake up. Setting noatime on the volume helped reduce load and iowait by a large amount, but still it shows up (and already caused two complete lockups within two hours).

To further add proof that it's btrfs causing issues: the following commands on shell took 15 seconds each (btrfs-transact was active both times)

mkdir /data/addons/config/sabnzbd/postproc
chown bas:admins /data/addons/config/sabnzbd/postproc/

Now, you can't in all seriousness tell me that a mkdir on shell taking that long could be caused by a potentially outdated unrar/par2/python package. It simply does not happen. It's the btrfs processes. At the same time as this is taking place, I see SQL errors on sabnzbd with the message that the database is locked. File system access is completely locked by btrfs wanting to be clever and snapshot stuff. I did disable snapshots on all shares (and antivirus too), but I doubt that disables the feature in btrfs.

Tomorrow I should receive a new 4GB ram unit for the box, maybe some more memory will improve things. It's worth a shot anyway. The only other reason besides memory and FS I can think of is failing hardware. Without a comparative test by someone else with a similar device, it's hard to say either way.