Public bug reported:
Using mylvmbackup 0.15, if you for example set "mycnf=/etc/mysql/my.cnf"
but that file is a symlink, like my.cnf -> /etc/alternatives/my.cnf, the
operation fails with
Error: Could not copy /etc/mysql/my.cnf to /var/cache/mylvmbackup/mnt
/backup-cnf-20170830_183218_mysql: File exists
strace:
lstat("/etc/mysql/my.cnf", {st_mode=S_IFLNK|0777, st_size=24, ...}) = 0
readlink("/etc/mysql/my.cnf", "/etc/alternatives/my.cnf", 4095) = 24
stat("/etc/alternatives/my.cnf", {st_mode=S_IFREG|0644, st_size=869, ...}) = 0
readlink("/etc/mysql/my.cnf", "/etc/alternatives/my.cnf", 4095) = 24
symlink("/etc/alternatives/my.cnf",
"/var/cache/mylvmbackup/mnt/backup-cnf-20170830_183218_mysql") = -1 EEXIST
(File exists)
** Affects: mylvmbackup
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1714045
Title:
fails to copy my.cnf if it is a symlink
To manage notifications about this bug go to:
https://bugs.launchpad.net/mylvmbackup/+bug/1714045/+subscriptions
--
Mailing list: https://launchpad.net/~enterprise-support
Post to : [email protected]
Unsubscribe : https://launchpad.net/~enterprise-support
More help : https://help.launchpad.net/ListHelp
