Dear all,
Every night I receive lots of messages like this in my event log :
My investigations demonstrated that the scheduled jobs running at the same moment are 2 heavy rsync jobs (over ssh) performed by a remote machine in order to backup things on file space located within a regular FreeBSD jail. (rsync -avz of > 60GB of data).
Network access to this jail is done through the main network Internet interface and thanks to an IPinIP tunnel (gif interface) routing RFC1918 traffic up to the jail.
A top performed every minute while the job is running shows that the physical memory is not impacted but there is a quick reduction of available swap space as soon as the jobs start.
This swap space never falls to 0. So the kernel seems to fail to allocate swap space at the rate it's being requested by the 2 rsync jobs.
This Jail is never updated while the host gets updated regularly.
Currently the host is running FreeBSD 10.1-RELEASE-p25 FreeBSD 10.1-RELEASE-p25 #7 r291865: Sat Dec 5 21:30:52 CET 2015 amd64
Rsync version in the jail : rsync version 3.1.1 protocol version 31
Any idea what could cause this swap issue ?
Thanks !
a.
Every night I receive lots of messages like this in my event log :
Code:
swap_pager_getswapspace(2): failed
swap_pager_getswapspace(3): failed
swap_pager_getswapspace(2): failed
swap_pager_getswapspace(2): failed
swap_pager_getswapspace(4): failed
swap_pager_getswapspace(5): failed
swap_pager_getswapspace(2): failed
swap_pager_getswapspace(3): failed
swap_pager_getswapspace(2): failed
My investigations demonstrated that the scheduled jobs running at the same moment are 2 heavy rsync jobs (over ssh) performed by a remote machine in order to backup things on file space located within a regular FreeBSD jail. (rsync -avz of > 60GB of data).
Network access to this jail is done through the main network Internet interface and thanks to an IPinIP tunnel (gif interface) routing RFC1918 traffic up to the jail.
A top performed every minute while the job is running shows that the physical memory is not impacted but there is a quick reduction of available swap space as soon as the jobs start.
This swap space never falls to 0. So the kernel seems to fail to allocate swap space at the rate it's being requested by the 2 rsync jobs.
This Jail is never updated while the host gets updated regularly.
Currently the host is running FreeBSD 10.1-RELEASE-p25 FreeBSD 10.1-RELEASE-p25 #7 r291865: Sat Dec 5 21:30:52 CET 2015 amd64
Rsync version in the jail : rsync version 3.1.1 protocol version 31
Any idea what could cause this swap issue ?
Thanks !
a.