Updatedb messing with backups..

Discussion in 'Proxmox VE 1.x: Installation and configuration' started by marotori, Dec 1, 2011.

  1. marotori

    marotori Member

    Joined:
    Jun 17, 2009
    Messages:
    161
    Likes Received:
    0
    This may have come up before.. but I thought worth mentioning.

    If you occasionally have backups using the vzdump system fail - because the /mnt/pve/vzsnap folder could not be unmounted...The issue is most likely the mlocate cron job traversing this mount point.The fix is very simple - and really should be included by default from the install cdrom.

    edit: /etc/updatedb.conf

    Change this line:pRUNEPATHS="/tmp /var/spool /media /mnt/pve"

    To include the path /mnt/pve

    Job done.

    Now future snapshot backups will not get locked down by the files being open - and then not being able to unmount the file system!

    Rob
     
  2. jekader

    jekader Member

    Joined:
    Feb 11, 2011
    Messages:
    77
    Likes Received:
    0
    Thanks for the tip! Got me wondering why vzsnap0 doesn't always get unmounted.
    Although this way I won't be able to find the images I need, since currently I'm using
    locate <VMID> | grep raw

    :rolleyes:
    Maybe it would be better to exclude /mnt/vzsnap0 instead?
     
  3. marotori

    marotori Member

    Joined:
    Jun 17, 2009
    Messages:
    161
    Likes Received:
    0
    You could always do a:

    find /var/lib/vz -name "*id*"

    Or... Just make sure the cron for mlocate runs at a time that does not interfere!

    Rob




    Sent from my iPhone using Tapatalk
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice