[PVE-User] Filesystem corruption on a VM?

Marco Gaiarin gaio at sv.lnf.it
Thu Nov 15 14:24:20 CET 2018


Mandi! Daniel Berteaud
  In chel di` si favelave...

> If at one time, the storage pool went out of space, then the FS is most
> likely corrupted. Fixing the space issue will prevent further
> corruption, but won't fix the already corrupted FS. You said

But *I* fix every day FS corruption! Every night i reboot the VMs that
have:
	fsck.mode=force

as grub boot parameters. In logs, i can se that FS get fixed.

	Nov 13 23:44:20 vdmsv1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-amd64 root=UUID=587fe965-e914-4c0b-a497-a0c71c7e0301 ro quiet fsck.mode=force
	Nov 13 23:44:20 vdmsv1 systemd-fsck[644]: /dev/sda6: 15062/8495104 files (3.0% non-contiguous), 1687411/33949952 blocks
	Nov 13 23:44:20 vdmsv1 systemd-fsck[647]: /dev/sdb1: 113267/6553600 files (1.9% non-contiguous), 1590050/26214144 blocks


> Anyway, If errors come back after reformating the volume, then you still
> have something not fixed.

Reading the Ubuntu, Debian and RH bugs in my initial posts, seems to me
that this is not the case.
The trouble seems exactly the same: same errors, same partial fix
incrementing the available RAM to the VM.


> Please tell us how are things configured, what
> kind of storage it's using, which layers are involved etc... (thin prov,
> iSCSI, LVM on top etc...)

HS MSA 1040 SAN, exporting iSCSI volumes via LVM. The 'thin' part is on
the SAN side, eg no thin-LVM, no ZFS on top of it, ...


Another error popup now:

 Nov 15 13:44:44 vdmsv1 kernel: [136834.664486] EXT4-fs error (device sda6): ext4_mb_generate_buddy:759: group 957, block bitmap and bg descriptor inconsistent: 32747 vs 32768 free clusters
 Nov 15 13:44:44 vdmsv1 kernel: [136834.671565] EXT4-fs error (device sda6): ext4_mb_generate_buddy:759: group 958, block bitmap and bg descriptor inconsistent: 32765 vs 32768 free clusters
 Nov 15 13:44:44 vdmsv1 kernel: [136834.813465] JBD2: Spotted dirty metadata buffer (dev = sda6, blocknr = 0). There's a risk of filesystem corruption in case of system crash.

increasing the VM ram from 8 to 12 GB lead to a 1,5 day interval between
errors, while before errors was every 'less than a day'.


This night another 4GB of RAM, another stop and start, ...

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''          http://www.lanostrafamiglia.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
      http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)



More information about the pve-user mailing list