unable to run e2fsck because of MMP

Pca

New Member
Jul 1, 2021
19
1
1
Hello

we have the rootfs in a lxc which has to be repaired.
the lxc has been stopped. then pct fsck ran but complained we have to do the fsck manually.
but when I do it complains with MMP like this :

: e2fsck /var/lib/vz/images/236/vm-236-disk-1.raw e2fsck 1.43.4 (31-Jan-2017) e2fsck: MMP: open with O_DIRECT failed while reading MMP block /var/lib/vz/images/236/vm-236-disk-1.raw: ********** WARNING: Filesystem still has errors **********

I am unable to clear the MMP flags :

root@pmx019 [~]: tune2fs -E clear_mmp /var/lib/vz/images/236/vm-236-disk-1.raw tune2fs 1.43.4 (31-Jan-2017) tune2fs: MMP: open with O_DIRECT failed while trying to open /var/lib/vz/images/236/vm-236-disk-1.raw Couldn't find valid filesystem superblock.

I can dump the FS :
: dumpe2fs /var/lib/vz/images/236/vm-236-disk-1.raw | head -65 dumpe2fs 1.43.4 (31-Jan-2017) Filesystem volume name: <none> Last mounted on: /mnt/vzsnap0 Filesystem UUID: d660b2de-6e08-4518-b0cb-74d8a9ddcae2 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent mmp flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 6553600 Block count: 26214400 Reserved block count: 1310720 Free blocks: 12630127 Free inodes: 6495917 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 1017 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Mon Oct 3 11:05:24 2016 Last mount time: Mon Nov 15 19:18:37 2021 Last write time: Mon Nov 15 19:18:37 2021 Mount count: 75 Maximum mount count: -1 Last checked: Mon Oct 3 11:05:24 2016 Check interval: 0 (<none>) Lifetime writes: 6052 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: d3387f6b-0455-4b94-a98e-9e5d91000544 Journal backup: inode blocks FS Error count: 1144 First error time: Mon Nov 14 18:05:55 2016 First error function: htree_dirblock_to_tree First error line #: 987 First error inode #: 413563 First error block #: 1591759 Last error time: Sun Nov 14 01:24:15 2021 Last error function: ext4_lookup Last error line #: 1594 Last error inode #: 3803475 Last error block #: 0 MMP block number: 9255 MMP update interval: 5 Journal features: journal_incompat_revoke Journal size: 128M Journal length: 32768 Journal sequence: 0x0168b08c Journal start: 0 Group 0: (Blocks 0-32767) csum 0x8be7 [ITABLE_ZEROED] Primary superblock at 0, Group descriptors at 1-7


I found nothing which has the FS opened on the pmx.
storage is NFS.


is there a way to get rid of this situation ?
 
pct shutdown 236
umount /var/lib/vz/images/236/vm-236-disk-1.raw
tune2fs -f -E clear_mmp /var/lib/vz/images/236/vm-236-disk-1.raw
 
  • Like
Reactions: Pca

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!