Hi experts,
my Samba container is planned to use file space from a dedicated disk. The disk is an LVM (for snapshot backup and the possibility to extend it later). I've read some postings and the Wiki about bind mounting LVMs and so I followed that description.
The Wiki is a bit fuzzy about the unmount script, so I tried with and without. Results:
System is:
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
Kind regards,
berni
my Samba container is planned to use file space from a dedicated disk. The disk is an LVM (for snapshot backup and the possibility to extend it later). I've read some postings and the Wiki about bind mounting LVMs and so I followed that description.
The Wiki is a bit fuzzy about the unmount script, so I tried with and without. Results:
- Without unmount: With each container restart (from proxmox Web interface), the disk gets mounted again, and /etc/mtab gets one additional line with the bind mount (n restarts = n+1 bind mount lines). But disk seems to be accessible. That looked a bit weird, so I tried:
- With unmount: After container restart, the disk is not (re)mounted. Neither in the container, nor on the host.
System is:
pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
Kind regards,
berni