|Subject:||Re: [rdiff-backup-users] rdiff-backup dies with ENOMEM due to requesting enormous amounts of memory|
|Date:||Fri, 10 Jun 2016 08:11:33 -0700|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0|
On 06/10/2016 04:34 AM, Patrik Dufresne wrote:|
Should be plenty:
$ free -m
total used free shared buff/cache available
Mem: 1869 172 1169 0 527 1538
Swap: 0 0 0
I'm trying to back up the root filesystem of a generic CentOS 7 box. It doesn't output that it even hit the filesystem yet though, it dies before that from what I can tell. It dies in the same way even when I try to back up a single empty directory.
$ python -V
Nothing in any logs other than simply showing someone logged in via SSH. The ENOMEM is /not/ on the remote side, it's on the side starting the backup and doing a pull from another server.
|[Prev in Thread]||Current Thread||[Next in Thread]|