Version 5 Development > Other
Mover causes complete crash (5b14)
ajburnet:
Hi all,
I first had this problem in December and have made no progress in resolving it. I tried re-building it using the latest plugins etc in the hope that it might be resolved - sadly the issue still exists. Id really like to have a cache drive that I can use!
So, I now have:
5b14 (Hardware: 4GB RAM, X2 2.6GHZ)
Plugins: APCUPSDaemon, Plex, SABnzbd, Couchpotato, SickBeard, rSYNC daemon (standalone) for rsync backups, powerdown script, unMENU
I have tried disabling these one by one and no change. The output of a tail run is included below.
Any ideas??! Thank you all!!
Alex.
BRiT:
Have you ensured your system is stable enough to complete a couple hours run of Memtest?
WeeboTech:
I think you are running out of ram. Even though you have 4GB, you are running out of low ram.
Are you running cache_dirs?
you could try dropping the cache's before the mover starts.
put this in the start of the mover script and duplicate it at the end of the script.
echo 3 > /proc/sys/vm/drop_caches
When does your rsync backup occur?
You may to do this command to drop the cache before and after it.
I know you have 4gb, but I have the same issue because I have so many files.
If I were to run cache_dirs and one of my system backups without dropping the cache I would see these types of crashes also.
There are other tunings you can try. Download my rsync_linked_backup script from my google code page.
There's an example of what I do before the rsync and after it.
Here's a snippet.
--- Code: ---# Save Kernel Options.
swappiness=$(</proc/sys/vm/swappiness)
cachepressure=$(</proc/sys/vm/vfs_cache_pressure)
echo 3 > /proc/sys/vm/drop_caches
echo 100 > /proc/sys/vm/swappiness
echo 200 > /proc/sys/vm/vfs_cache_pressure
nice ionice -c3 rsync -aW ${RSYNCOPTS} ${BACKUPSRC[*]} ${BACKUPDIRD}
echo 3 > /proc/sys/vm/drop_caches
echo $swappiness > /proc/sys/vm/swappiness
echo $cachepressure > /proc/sys/vm/vfs_cache_pressure
--- End code ---
ajburnet:
Thanks - yes, I've run an overnight memtest and all was okay.
I'll try your script and report back! Thanks.
WeeboTech:
--- Quote from: ajburnet on February 25, 2012, 04:37:28 PM ---Thanks - yes, I've run an overnight memtest and all was okay.
I'll try your script and report back! Thanks.
--- End quote ---
You need to modify your mover script manually.
Then save the changes somewhere on your boot drive.
FWIW, this only bandaid's the problem.
If the root filesystem was on tmpfs and you had a swap file you might not encounter this.
Do your extra programs use /tmp for anything?
If so you may want to reconfigure them to use /mnt/cache/.tmp or something like that.
Do you have a swap partition or swap file on the cache drive anywhere?
Navigation
[0] Message Index
[#] Next page
Go to full version