LXC-Container startet nicht mehr nach stoppen - CIFS-Handle leer?

Sep 21, 2023
5
0
1
Hallo Community,

ich hab ein merkwürdiges Problem. Ich hab ne kleine Proxmoxinstallation, zwei VMs, ein Container (LXC). Als Storage sind per CIFS ein paar Mountpoints von meiner DiskStation eingebunden.
Wenn ich den LXC-Container stoppe, kann ich ihn danach nicht mehr starten. Grund ist jeweils
lxc_init: 844 Failed to run lxc.hook.pre-start for container "101"
Hab mit lxc-start mir mal mehr loggen lassen, faktisch hat er jedes Mal keine CIFS-Writehandles:
lxc-start 101 20231109091534.530 DEBUG conf - ../src/lxc/conf.c:run_buffer:311 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 101 lxc pre-start produced output: mount: /var/lib/lxc/.pve-staged-mounts/rootfs: can't read superblock on /dev/loop0.
der dmesg-Auszug dazu:
[ 3769.919021] CIFS: VFS: No writable handle in writepages rc=-9

Ich muss die Node neustarten, damit ich den Container gestartet bekommen - woran liegt das? Warum fehlen Handle?
 
Ich hab weiter rumgetestet.
Mein Container hat seine root-disk auf der DiskStation, genauso ein zusätzlicher Mountpoint.
Ich wollte die CIFS-Ressourcen ausschließen aus dem Problem, also wollte ich den Container auf die lokale Platte clonen (bei den zusätzlichen Mountpoint hab ich den Haken bei "Backup" entfernt - der wird im Container eh nicht aktiv verwendet außer eingebunden zu sein).
Aber auch das mag nicht klappen.
Ich habe per WebUI den Klonen-Dialog gestartet und ein lokales Storage mit genug Platz angegeben. Folgender Fehler kommt dann:

Code:
create full clone of mountpoint mp0 (nextcloud_data:101/vm-101-disk-0.raw)
Formatting '/var/lib/vz/images/103/vm-103-disk-0.raw', fmt=raw size=536870912000 preallocation=off
Creating filesystem with 131072000 4k blocks and 32768000 inodes
Filesystem UUID: 93612a95-a076-4e15-a303-dc2213f4d2a4
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
    4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,

Number of files: 4 (reg: 1, dir: 3)
Number of created files: 2 (reg: 1, dir: 1)
Number of deleted files: 0
Number of regular files transferred: 1
Total file size: 0 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 0
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 233
Total bytes received: 50

sent 233 bytes  received 50 bytes  566.00 bytes/sec
total size is 0  speedup is 0.00
create full clone of mountpoint rootfs (Default:101/vm-101-disk-0.raw)
Formatting '/var/lib/vz/images/103/vm-103-disk-1.raw', fmt=raw size=25769803776 preallocation=off
Creating filesystem with 6291456 4k blocks and 1572864 inodes
Filesystem UUID: 027fe805-99f7-47e9-88b0-897869fcd4f2
Superblock backups stored on blocks:
    32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
mount: /var/lib/lxc/103/.copy-volume-2: cannot mount /dev/loop0 read-only.
       dmesg(1) may have more information after failed mount system call.
Specified filename /var/lib/lxc/103/.copy-volume-1 does not exist.
TASK ERROR: clone failed: command 'mount -o ro /dev/loop0 /var/lib/lxc/103/.copy-volume-2//' failed: exit code 32

Vielleicht kann damit jemand einen hilfreichen Tipp geben, es dreht sich immer wieder um loop0, ich kann aber nicht so recht rausbekommen, in welche Richtung ich weiterbohrens soll. Es ist echt frustrierend, ich mach ja nix Kompliziertes, das ist nen stumpfer debian-Container :(

Hinweis: Bzgl. dem Klonen ist es egal, ob die Node frischgestartet ist oder nicht - es geht jedes Mal nicht, jedes Mal war der Container im Modus "stopped".

DMESG dazu sieht folgendermaßen aus:
Code:
[   20.582314] Key type cifs.spnego registered
[   20.582338] Key type cifs.idmap registered
[   20.582866] CIFS: Attempting to mount \\192.168.0.55\Proxmox_Next_Data
[   21.396971] CIFS: Attempting to mount \\192.168.0.55\Proxmox_Images
[   21.734991] CIFS: Attempting to mount \\192.168.0.55\Proxmox_Main
[   21.922630] kvm: vcpu 1: requested 53086 ns lapic timer period limited to 200000 ns
[   22.710628] usb 1-9: reset full-speed USB device number 4 using xhci_hcd
[  187.755788] loop0: detected capacity change from 0 to 1048576000
[  187.799360] EXT4-fs (loop0): mounted filesystem a5646586-e227-49f0-b046-2b788f54b1aa with ordered data mode. Quota mode: none.
[  187.813691] loop1: detected capacity change from 0 to 1048576000
[  187.842564] EXT4-fs (loop1): mounted filesystem 93612a95-a076-4e15-a303-dc2213f4d2a4 with ordered data mode. Quota mode: none.
[  187.939249] EXT4-fs (loop1): unmounting filesystem 93612a95-a076-4e15-a303-dc2213f4d2a4.
[  187.957899] EXT4-fs (loop0): unmounting filesystem a5646586-e227-49f0-b046-2b788f54b1aa.
[  188.104462] loop0: detected capacity change from 0 to 50331648
[  188.148260] EXT4-fs (loop0): INFO: recovery required on readonly filesystem
[  188.148263] EXT4-fs (loop0): write access unavailable, cannot proceed (try mounting with noload)
[ 1710.490646] loop0: detected capacity change from 0 to 1048576000
[ 1710.534758] EXT4-fs (loop0): mounted filesystem a5646586-e227-49f0-b046-2b788f54b1aa with ordered data mode. Quota mode: none.
[ 1710.549413] loop1: detected capacity change from 0 to 1048576000
[ 1710.575278] EXT4-fs (loop1): mounted filesystem 478baa2a-6438-4423-852c-b4e3c5aa414b with ordered data mode. Quota mode: none.
[ 1710.671312] EXT4-fs (loop1): unmounting filesystem 478baa2a-6438-4423-852c-b4e3c5aa414b.
[ 1710.689085] EXT4-fs (loop0): unmounting filesystem a5646586-e227-49f0-b046-2b788f54b1aa.
[ 1710.834486] loop0: detected capacity change from 0 to 50331648
[ 1710.878885] EXT4-fs (loop0): INFO: recovery required on readonly filesystem
[ 1710.878888] EXT4-fs (loop0): write access unavailable, cannot proceed (try mounting with noload
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!