While trying to do a backup We are getting a strange error:
when running mount I see:
I am thinking it would/should be safe to remove that snapshot via lvremove - but figured i should ask just in case:
Any thoughts?
Code:
trying to remove stale snapshot '/dev/pve/vzsnap-xanadu-three-0'
INFO: umount: /mnt/vzsnap0: not mounted
ERROR: command 'umount /mnt/vzsnap0' failed: exit code 1Code:
mount
/dev/mapper/pve-root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/pve-data on /var/lib/vz type ext3 (rw)
/dev/sda1 on /boot type ext3 (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,default_permissions,allow_other)
none on /sys/kernel/config type configfs (rw)
beancounter on /proc/vz/beancounter type cgroup (rw,name=beancounter)
container on /proc/vz/container type cgroup (rw,name=container)
fairsched on /proc/vz/fairsched type cgroup (rw,name=fairsched)
192.168.118.234:/mnt/threetb/xanadu-store-one on /mnt/pve/xanadu-nfs type nfs (rw,vers=3,addr=192.168.118.234)
192.168.119.234:/mnt/threetb/windows7CCNET on /mnt/pve/windows7CCNET type nfs (rw,vers=3,addr=192.168.119.234)
192.168.117.234:/mnt/RAIDF/mysqlbackups/mysqlbackups on /mnt/pve/sqlBackups type nfs (rw,vers=3,addr=192.168.117.234)Code:
#lvdisplay
--- Logical volume ---
LV Path /dev/pve/swap
LV Name swap
VG Name pve
LV UUID 00era5-CCUo-h9KZ-eImv-rLL8-Sjrq-W53zSd
LV Write Access read/write
LV Creation host, time proxmox, 2012-06-10 23:15:45 -0400
LV Status available
# open 1
LV Size 15.00 GiB
Current LE 3840
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1
--- Logical volume ---
LV Path /dev/pve/root
LV Name root
VG Name pve
LV UUID GpgBC4-XKXG-f4YZ-nA4w-wgYG-agKA-TZQ7P1
LV Write Access read/write
LV Creation host, time proxmox, 2012-06-10 23:15:45 -0400
LV Status available
# open 1
LV Size 96.00 GiB
Current LE 24576
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
--- Logical volume ---
LV Path /dev/pve/data
LV Name data
VG Name pve
LV UUID eGyeca-EdOU-h8U1-cKzt-75Xv-R4JO-CAXKbI
LV Write Access read/write
LV Creation host, time proxmox, 2012-06-10 23:15:46 -0400
LV snapshot status source of
vzsnap-xanadu-three-0 [INACTIVE]
LV Status available
# open 1
LV Size 1.69 TiB
Current LE 444293
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3
--- Logical volume ---
LV Path /dev/pve/vzsnap-xanadu-three-0
LV Name vzsnap-xanadu-three-0
VG Name pve
LV UUID U7udiI-vk0V-QPOS-0qYn-VThj-r5cM-nFmgxO
LV Write Access read/write
LV Creation host, time xanadu-three, 2012-12-12 10:03:49 -0500
LV snapshot status INACTIVE destination for data
LV Status available
# open 0
LV Size 1.69 TiB
Current LE 444293
COW-table size 1.00 GiB
COW-table LE 256
Snapshot chunk size 4.00 KiB
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:5Any thoughts?