Avamar: Avamar FLR fails on Linux XFS filesystem using on-disk format (v5) xfs feature
Summary: Avamar: Avamar FLR fails on Linux XFS filesystem using on-disk format (v5) xfs feature
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
When browsing newer linux virtual machine distribution (example RHEL7.3+ or SLES12+) whose guest filesystem are formated xfs filesystems FLR mount will fail on Avamar proxy 7.5.0 and lower:
1. Failed to mount disks. Verify that all the disks on the VM have valid/supported partitions.
Or
2. Failed to change physical volume UUID.
Or
3. Not all linux mounts are properly being disabled in the Avamar GUI after browse.
On the proxy the FLR browse/mount logs show the following:
/usr/local/avamarclient/bin/MountPoint/logs/<randomuuid.log> [MP - DEBUG] <date> TID=20315 MID=268: sCmdline = /sbin/blkid ... [MP - DEBUG] <date> TID=20315 MID=277: sLine = /dev/loop4: UUID="e46da391-6b69-48b5-8227-e9bc628df877" TYPE="xfs" ... [MP - DEBUG] <date> TID=20315 MID=289: sCmdline = /bin/mount -t xfs /dev/loop4 /tmp/MntPnt12D3P0 [MP - DEBUG] <date> TID=20315 MID=290: sLine = mount: wrong fs type, bad option, bad superblock on /dev/loop4, [MP - DEBUG] <date> TID=20315 MID=291: sLine = missing codepage or helper program, or other error [MP - DEBUG] <date>TID=20315 MID=292: sLine = In some cases useful info is found in syslog - try [MP - DEBUG] <date> TID=20315 MID=293: sLine = dmesg | tail or so
Cause
Avamar 7.5.0 and lower proxies are built using SLES 11.SP3 which which does not support XFS V5 : This is because proxy are using: Kernel version 3.0.76 and Xfsprogs version xfsprogs-3.1.8
Newer linux distribution which use XFS has a new xfs feature on-disk format (v5) More info can be found here: https://wiki.archlinux.org/index.php/XFS
As noted in the link above the proxy kernel version would have to be 3.1.6 or higher to support this feature.
To check if virtual machine is using this xfs feature run this command xfs_db command on the live vm and check for FTYPE flag:
Examples
1. File system with feature Disabled ( FLR would work)
Newer linux distribution which use XFS has a new xfs feature on-disk format (v5) More info can be found here: https://wiki.archlinux.org/index.php/XFS
As noted in the link above the proxy kernel version would have to be 3.1.6 or higher to support this feature.
To check if virtual machine is using this xfs feature run this command xfs_db command on the live vm and check for FTYPE flag:
Examples
1. File system with feature Disabled ( FLR would work)
# xfs_db -r -c version /dev/sdb1 versionnum [0xb4a4+0xa] = V4,NLINK,DIRV2,ALIGN,LOGV2,EXTFLG,MOREBITS,ATTR2,LAZYSBCOUNT
2. Filesystem with Feature Enabled: ( FLR would FAIL) due to "FTYPE" feature
# xfs_db -r -c version /dev/sdb2 versionnum [0xb4a4+0x28a] = V4,NLINK,DIRV2,ALIGN,LOGV2,EXTFLG,MOREBITS,ATTR2,LAZYSBCOUNT,PROJID32BIT,FTYPE
Resolution
Redeploy the Avamar proxies to 7.5.1 or higher.
This proxy release is the first proxy to use SLES 12 SP1 OS platform which has native support for XFS v5 per the Avamar 7.5.1 release notes:
Avamar VMware support enhancement:
File-level restore support for browsing and restoring Linux-based BTRFS and XFS v5 file systems.
This proxy release is the first proxy to use SLES 12 SP1 OS platform which has native support for XFS v5 per the Avamar 7.5.1 release notes:
Avamar VMware support enhancement:
File-level restore support for browsing and restoring Linux-based BTRFS and XFS v5 file systems.
Additional Information
For RHEL8 or similar see kb 538905.
Affected Products
AvamarProducts
AvamarArticle Properties
Article Number: 000167471
Article Type: Solution
Last Modified: 05 Nov 2024
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.