holland-coredev team mailing list archive

[Andrew Garner <715426@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

If a mysql datadir  is on a LVM enabled / and we attempt to determine
the datadir relative to its (root) mountpoint, we get a bad relative
path:

>>> from holland.lib.lvm.util import relpath
>>> relpath('/var/lib/mysql', '/')
'../var/lib/mysql'

This causes $snapshot_mountpoint/$relpath to be an non-existent
directory  for instance /tmp/XXXXX/../var/lib/mysql =>
/tmp/var/lib/mysql/ which is invalid.

This is actually a python bug with os.path.relpath:

http://bugs.python.org/issue5117

** Affects: holland-backup
     Importance: Critical
     Assignee: Andrew Garner (muzazzi)
         Status: In Progress

** Changed in: holland-backup
   Importance: Undecided => Critical

** Changed in: holland-backup
       Status: New => In Progress

** Changed in: holland-backup
     Assignee: (unassigned) => Andrew Garner (muzazzi)

** Changed in: holland-backup
    Milestone: None => 1.0.8

-- 
You received this bug notification because you are a member of Holland
Discuss, which is subscribed to holland-backup.
https://bugs.launchpad.net/bugs/715426

Title:
  mysql-lvm does not calculate paths relative to / correctly

Status in Holland Backup Framework:
  In Progress

Bug description:
  If a mysql datadir  is on a LVM enabled / and we attempt to determine
  the datadir relative to its (root) mountpoint, we get a bad relative
  path:

  >>> from holland.lib.lvm.util import relpath
  >>> relpath('/var/lib/mysql', '/')
  '../var/lib/mysql'

  This causes $snapshot_mountpoint/$relpath to be an non-existent
  directory  for instance /tmp/XXXXX/../var/lib/mysql =>
  /tmp/var/lib/mysql/ which is invalid.

  This is actually a python bug with os.path.relpath:

  http://bugs.python.org/issue5117