XFS file-restore

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
Hi!

I am trying to file-restore from disk with XFS file system:


xfs.png

XFS not supported in PBS?

PBS package versions:
proxmox-backup: 1.0-4 (running kernel: 5.4.114-1-pve) proxmox-backup-server: 1.1.9-1 (running version: 1.1.9) pve-kernel-5.4: 6.4-2 pve-kernel-helper: 6.4-2 pve-kernel-5.4.114-1-pve: 5.4.114-1 pve-kernel-5.4.106-1-pve: 5.4.106-1 ifupdown2: 3.0.0-1+pve3 libjs-extjs: 6.0.1-10 proxmox-backup-docs: 1.1.9-1 proxmox-backup-client: 1.1.9-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.5-6 pve-xtermjs: 4.7.0-3 smartmontools: 7.2-pve2 zfsutils-linux: 2.0.4-pve1

Code:
# pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.114-1-pve)
pve-manager: 6.4-6 (running version: 6.4-6/be2fa32c)
pve-kernel-5.4: 6.4-2
pve-kernel-helper: 6.4-2
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
ceph: 14.2.20-pve1
ceph-fuse: 14.2.20-pve1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-2
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.6-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-5
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-3
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

---
Best regards!
Gosha
 

Attachments

  • xfs.png
    xfs.png
    67.4 KB · Views: 5
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
5,852
613
133
32
Vienna
xfs works normally here, how does a 'mount' look like inside your vm? also the log from /var/log/proxmox-backup/file-restore/qemu.log would be interesting
 

fpausp

Well-Known Member
Aug 31, 2010
454
26
48
Austria near Vienna
how does a 'mount' look like inside your vm?
Code:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=1928128k,nr_inodes=482032,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio,net_cls)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mapper/VolGroup-lv_root on / type xfs (rw,relatime,attr2,inode64,noquota)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=35,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12950)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
/dev/sda1 on /boot type xfs (rw,relatime,attr2,inode64,noquota)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=387988k,mode=700)

the log from /var/log/proxmox-backup/file-restore/qemu.log
Code:
[2021-06-07T09:24:05+02:00] PBS file restore VM log
[init-shim] beginning user space setup
[init-shim] debug: agetty start failed: /sbin/agetty not found, probably not running debug mode and safe to ignore
[init-shim] reached daemon start after 0.43s
[2021-06-07T07:24:05Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi0'): found partition '/dev/vda2' (2, 804231577600B)
[2021-06-07T07:24:05Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi0'): found partition '/dev/vda1' (1, 1073741824B)
[2021-06-07T07:24:05Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] Supported FS: reiserfs, ext3, ext4, ext2, vfat, msdos, iso9660, hfsplus, hfs, sysv, v7, ntfs, ufs, jfs, xfs, befs, f2fs, btrfs
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (reiserfs) - EINVAL: Invalid argument
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ext3) - EINVAL: Invalid argument
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ext4) - EINVAL: Invalid argument
EXT2-fs (vda2): error: can't find an ext2 filesystem on dev vda2.
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ext2) - EINVAL: Invalid argument
FAT-fs (vda2): bogus number of reserved sectors
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (vfat) - EINVAL: Invalid argument
FAT-fs (vda2): bogus number of reserved sectors
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (msdos) - EINVAL: Invalid argument
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (iso9660) - EINVAL: Invalid argument
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (hfsplus) - EINVAL: Invalid argument
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (hfs) - EINVAL: Invalid argument
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (sysv) - EINVAL: Invalid argument
VFS: could not find a valid V7 on vda2.
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (v7) - EINVAL: Invalid argument
ntfs: (device vda2): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vda2): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vda2): ntfs_fill_super(): Not an NTFS volume.
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ntfs) - EINVAL: Invalid argument
ufs: ufs_fill_super(): bad magic number
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ufs) - EINVAL: Invalid argument
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (jfs) - EINVAL: Invalid argument
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (xfs) - EINVAL: Invalid argument
befs: (vda2): invalid magic header
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (befs) - EINVAL: Invalid argument
F2FS-fs (vda2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda2): Can't find valid F2FS filesystem in 2th superblock
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (f2fs) - EINVAL: Invalid argument
[2021-06-07T07:24:09Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (btrfs) - EINVAL: Invalid argument
[2021-06-07T07:24:09Z ERROR proxmox_backup::server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTAuaW1nLmZpZHgvcGFydC8y: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-scsi0.img.fidx/part/2' failed: all mounts failed or no supported file system

No XFS mount on vda2?
 
Last edited:

fabian

Proxmox Staff Member
Staff member
Jan 7, 2016
5,571
925
163
you use XFS on LVM - the LVM part is what is not yet supported.
 
  • Like
Reactions: fpausp

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
xfs works normally here, how does a 'mount' look like inside your vm? also the log from /var/log/proxmox-backup/file-restore/qemu.log would be interesting

Wow! The original question was asked by me. :)
And I don't know why fpausp answers the question asked to me :)
But I'll try to answer too:

mount in VM look as:

cat /etc/fstab
...
UUID=a4665bab-36b0-4534-bc1f-1e7ad2facf89 /var/samba/pub xfs defaults 0 2

# mount | grep sdb
...
/dev/sdb1 on /var/samba/pub type xfs (rw,relatime,attr2,inode64,noquota)


And where do I need to look /var/log/proxmox-backup/file-restore/qemu.log ?

On PBS:
cat /var/log/proxmox-backup/file-restore/qemu.log
cat: /var/log/proxmox-backup/file-restore/qemu.log: No such file or directory


On node with running VM: the same "No such file or directory"

---
Best regards!
Gosha

P.S. and I don't use LVM :)
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
5,852
613
133
32
Vienna
And where do I need to look /var/log/proxmox-backup/file-restore/qemu.log ?
on the pve node after you started the file-restore

proxmox-backup-client: 1.1.6-2
can you post the output of

dpkg -l | grep proxmox-backup

maybe the packages are too old, i think i remember some bug where we forgot some mount options
 

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
dpkg -l | grep proxmox-backup

maybe the packages are too old, i think i remember some bug where we forgot some mount options

for PBS:
# dpkg -l | grep proxmox-backup
ii proxmox-backup 1.0-4 all Proxmox Backup Server metapackage
ii proxmox-backup-client 1.1.9-1 amd64 Proxmox Backup Client tools
ii proxmox-backup-docs 1.1.9-1 all Proxmox Backup Documentation
ii proxmox-backup-server 1.1.9-1 amd64 Proxmox Backup Server daemon with tools and GUI

for PVE:
# dpkg -l | grep proxmox-backup
ii libproxmox-backup-qemu0 1.0.3-1 amd64 Proxmox Backup Server client library for QEMU
ii proxmox-backup-client 1.1.6-2 amd64 Proxmox Backup Client tools
ii proxmox-backup-file-restore 1.1.6-2 amd64 Proxmox Backup single file restore tools for pxar and block device backups
ii proxmox-backup-restore-image 0.2.1

screen.png


---
Best regards!
Gosha
 
Last edited:

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
dpkg -l | grep proxmox-backup

maybe the packages are too old, i think i remember some bug where we forgot some mount options


just updated packages for PVE:

# dpkg -l | grep proxmox-backup
ii libproxmox-backup-qemu0 1.0.3-1 amd64 Proxmox Backup Server client library for QEMU
ii proxmox-backup-client 1.1.8-1 amd64 Proxmox Backup Client tools
ii proxmox-backup-file-restore 1.1.8-1 amd64 Proxmox Backup single file restore tools for pxar and block device backups
ii proxmox-backup-restore-image 0.2.2 amd64 Kernel/initramfs images for Proxmox Backup single-file restore.

But still this error...


---
Best regards!
Gosha
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
5,852
613
133
32
Vienna
But still this error...
ok and the log? i do not see how that log does not get created, if its still not there can you do
Code:
ls -lhaR /var/log/proxmox-backup

?
 

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
ok and the log? i do not see how that log does not get created, if its still not there can you do
Code:
ls -lhaR /var/log/proxmox-backup

?

# ls -lhaR /var/log/proxmox-backup

ls: cannot access '/var/log/proxmox-backup': No such file or directory

:(
 

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
can you please check on the pve node on which you connect?

This was checked on a node with a running VM (for which a file-restore was made).
The same as I have already provided a screenshot (two my messages above)
 
Last edited:

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
5,852
613
133
32
Vienna
well i don't know what to say, the file-restore definitely writes into that logfile, and that will most likely contain the source of the original error
maybe check your other cluster nodes for the logs?

looking at the code it would fail much earlier when it could not create the logfile (it would not even be possible to list the partitions) so they have to be somewhere....
 

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
well i don't know what to say, the file-restore definitely writes into that logfile, and that will most likely contain the source of the original error
maybe check your other cluster nodes for the logs?

looking at the code it would fail much earlier when it could not create the logfile (it would not even be possible to list the partitions) so they have to be somewhere....

I just tested on the other three nodes. On one of them I found:

# cat /var/log/proxmox-backup/file-restore/qemu.log
[2021-06-08T08:24:16Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdd' ('drive-scsi3'): found partition '/dev/vdd1' (1, 53686042624B)
[2021-06-08T08:24:16Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi5'): found partition '/dev/vdb1' (1, 10736369664B)
[2021-06-08T08:24:16Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdg' ('drive-scsi0'): found partition '/dev/vdg1' (1, 10268704768B)
[2021-06-08T08:24:16Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdg' ('drive-scsi0'): found partition '/dev/vdg2' (2, 467664896B)
[2021-06-08T08:24:16Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vde' ('drive-scsi2'): found partition '/dev/vde1' (1, 14746267648B)
[2021-06-08T08:24:16Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-scsi4'): found partition '/dev/vdc1' (1, 10736369664B)
[2021-06-08T08:24:16Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi6'): found partition '/dev/vda1' (1, 10736369664B)
[2021-06-08T08:24:16Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] Supported FS: reiserfs, ext3, ext4, ext2, vfat, msdos, iso9660, hfsplus, hfs, sysv, v7, ntfs, ufs, jfs, xfs, befs, f2fs, btrfs
watchdog expired, shutting down
reboot: Power down


But this seems to apply to other backups...
 

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
well i don't know what to say, the file-restore definitely writes into that logfile, and that will most likely contain the source of the original error
maybe check your other cluster nodes for the logs?

looking at the code it would fail much earlier when it could not create the logfile (it would not even be possible to list the partitions) so they have to be somewhere....
Hi!

Assumption only. Maybe I need to install some package from PBS to PVE?

---
Best regards!
Gosha
 

dcsapak

Proxmox Staff Member
Staff member
Feb 1, 2016
5,852
613
133
32
Vienna
Maybe I need to install some package from PBS to PVE?
no, if the file-restore from the gui is already working, all packages that are needed are already installed...

i am honestly really baffled as to why the logs are not there...

just to check, you always started the file-restore before checking if the logfiles are there?
 

gosha

Active Member
Oct 20, 2014
298
18
38
Russia
just to check, you always started the file-restore before checking if the logfiles are there?

Yes, in all cases I ran the file recovery in the GUI first, and then tried to see the logfile (on node with this VM).

Since I was updating:

# dpkg -l | grep proxmox-backup
ii libproxmox-backup-qemu0 1.0.3-1 amd64 Proxmox Backup Server client library for QEMU
ii proxmox-backup-client 1.1.8-1 amd64 Proxmox Backup Client tools
ii proxmox-backup-file-restore 1.1.8-1 amd64 Proxmox Backup single file restore tools for pxar and block device backups
ii proxmox-backup-restore-image 0.2.2 amd64 Kernel/initramfs images for Proxmox Backup single-file restore.

may I need to restart the PVE cluster? I did not reboot, because I did not see the pve-kernel in the last updates.
But maybe I didn't notice ...
I can do reboot on Saturday.

---
Best regards!
Gosha
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE 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 your own in 60 seconds.

Buy now!