vzdump doesn't correctly handle sparse files.
I have 459G sparse file, that happens because I've implemented SSO based on FreeIPA, and users usually have high user id, and lastlog creates sparse file which gets as big as 459G.
As you can see file is actually only 16K but reports 459G
What FreeIPA user id look like:
So what happens, my storage only has about 200G free space, and because rsync runs without --sparse option it will copy it as a regular file, which means storage runs out of space.
Is there an option to add additional rsync args to the /etc/vzdump.conf or other options to work around that?
I have 459G sparse file, that happens because I've implemented SSO based on FreeIPA, and users usually have high user id, and lastlog creates sparse file which gets as big as 459G.
Code:
ipadmin@proxy:/var/log$ ls -slh lastlog
16K -rw-r--r-- 1 root root 459G Jul 28 13:58 lastlogAs you can see file is actually only 16K but reports 459G
What FreeIPA user id look like:
Code:
ipadmin@proxy:~$ id
uid=1687600003(ipadmin) gid=1687600003 groups=1687600003So what happens, my storage only has about 200G free space, and because rsync runs without --sparse option it will copy it as a regular file, which means storage runs out of space.
Is there an option to add additional rsync args to the /etc/vzdump.conf or other options to work around that?
