I've just built a new mysql server and have Amanda client installed and running on it. Dumps worked fine until I installed sssd and hooked the machine into our Active Direcotry domain (not my idea.)
Now, this link into Active Directory has bloated the /var/log/lastlog file up to something massive, and it's taking forever to get estimates for dumps from this machine, to the point that Amanda server gives up with a timeout error. The actual size of the file is only 52K, but its apparent size is 337G. I can strace tar (gnutar 1.27.1) and it's sitting there reading 512 blocks of zeroes. The --sparse option is on its command line. What I end up with is the client sendsize operation completes after 38 minutes, but the Amanda server's planner never notices and doesn't proceed past that point. I've looked in the planner log files and I don't know what to make of it, the planner never mentions receiving the size estimates back from the mysql server. The other partitions on this server backup just fine, it's only the root partition with this sparse lastlog file on it that is failing to dump. So, questions: Is gnu tar 1.27.1 compatible? I don't see any bug reports regarding its handling of sparse files. This version isn't listed in the FAQ, that table stops with gnu tar 1.26. Is kernel 4.2 an issue? I know that it has a new SEEK_HOLE thing that gnu tar isn't using yet, but supposedly bsdtar does use. I don't have any hosts using bsdtar. I see on Gnu's website that 1.29.1 supports it if you pass in -hole-detection as a new option, but that version isn't currently in Ubuntu 14.04 LTS yet. I'll just exclude the lastlog file from backups if I have to, but I'd prefer not to do that. -- Joi Owen System Administrator Pavlov Media, Inc.
