Search results

Create a CentOS contanier but the swap is fixed to 1GB, the config is set to 2GB. Even executing a swapoff -a the value remains. Any ideas? Any idea? my container config: arch: amd64 cores: 4 hostname: oracle memory: 4096 nameserver: 1.1.1.1 net0...

:-( that's my problem then :-( I was thinking the space use was absolute, :-( thanks :-D

Mistery solved :-( there was no space left on /var/lib/vz! :-( The spaces was 0 on hn device. But I swear there was space left no much time ago, the raw images grow over time? I set the space for every image at the beginning the space should not change :-(

Most important question... how can I repair the corrupted images? :-( Thanks in advance :-)

:-D no problem :-) No, the hn uptime is uptime 11:34:30 up 117 days, 3:36, 2 users, load average: 1.02, 0.92, 0.71 I did get alerted because the filesystems on several containers change to ro status, no restarts, no problems till this situation. The fisical disks are ok! the smart test...

I tried and this is the result, obviously I must be doing it wrong... root@proxmox4-eu3:~# mount /dev/loop2 /mnt/ mount: /dev/loop2: can't read superblock Because the pct start command start the container.

Can I use the /dev/loop2 device?

Hello, I stopped a container and issue the command, this is the response: root@proxmox4-eu3:~# partx -va /var/lib/vz/images/102/vm-102-disk-1.raw partition: none, disk: /var/lib/vz/images/102/vm-102-disk-1.raw, lower: 0, upper: 0 Trying to use '/dev/loop9' for the loop device partx...

:-o Thanks :-) How can I run the fsck command? How can I check? Mounting the image and then runing fsck? How can I mount the image? runing: mount -o loop .... like a .iso image? Thanks in advance Nomar

Good day: This is the situation, dmesg is reporting errors on loop devices (complete log on attachment), fsck on images show errors like this: root@proxmox4-eu3:~# e2fsck -fyv /var/lib/vz/images/107/vm-107-disk-1.raw e2fsck 1.42.12 (29-Aug-2014) MMP interval is 10 seconds and total wait time...

Thanks :-D

When you put 1T on the /etc/pve/lxc/102.conf file, this line on /var/lib/lxc/102: lxc.rootfs = loop:/var/lib/vz/images/102/vm-102-disk-1.raw ends like this: lxc.rootfs =

:-D no problem :-) Here we go: proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve) pve-manager: 4.0-48 (running version: 4.0-48/0d8559d0) pve-kernel-4.2.2-1-pve: 4.2.2-16 lvm2: 2.02.116-pve1 corosync-pve: 2.3.5-1 libqb0: 0.17.2-1 pve-cluster: 4.0-22 qemu-server: 4.0-30 pve-firmware: 1.1-7...

Thanks :-D

Not merely informational, if you put 1T on conf file, the config parser goes bananas and put a empty on the lxc generated config rootfs, that is the source of this error line: Use of uninitialized value $path in concatenation (.) or string at /usr/share/perl5/PVE/LXC.pm line 1110. When the...

Good grief: The error was in the config file, to the pct start script 1T and 1024G is not the same the problem whas there, changed the 1T to 1024G and the container start with no problem at all.

The output of dmesg | grep apparmor is [79613.533731] audit: type=1400 audit(1458998507.877:182): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/usr/bin/lxc-start" name="/" pid=2830 comm="lxc-start" flags="rw, rslave"

Good day: Have a lxc container and after a hardware node reboot the pve refuses to start, this is the pct start output root@proxmox4-eu0:~# pct start 102 Use of uninitialized value $path in concatenation (.) or string at /usr/share/perl5/PVE/LXC.pm line 1110. lxc-start: lxc_start.c: main: 344...

Re: Change default mount options to raw image * solved, sort of * Hi: I'm not sure about the battery-backed write cache on volume, meanwhile I migrate to postgresql backend and the performance improves a ton. Thanks anyway :-)

Good day I want to change the default mount options for a lxc container /images/102/vm-102-disk-1.raw on / type ext4 (rw,relatime,data=ordered) to improve db performance on bacula despooling they recommend use barrier=0 on mount options How can I configure this container with the...