Skip to main content

We recently ran in to an issue as noted here in the forums - Ubuntu Hardened Repository - Path is not XFS - Veeam R&D Forums

Has anyone seen this and come across a fix?  We are working with support on it but wanted to ask the community.  The server has been working fine and the path is definitely XFS as we validated everything.

Error -

 

Seems that Veeam cannot see the filesystem at all. The capacity and free space are shown as unknown, too.


Yes I know that but on the previous screen you can see the directory and sizing so it is there. 😉

 


I remember this from somewhere, but I'm not sure what the cause has been...Could it be that xfsinfo isn't installed on the system?


I remember this from somewhere, but I'm not sure what the cause has been...Could it be that xfsinfo isn't installed on the system?

Unsure but we are working with Support on the issue so will post back with the answer once we get one or workaround. 😄


For this case, it’s because the repository is looking for /backup but it’s not mounted. (However /backups is). 


Thanks for finding that out Hin and fixing our backups.  👍🏼


For this case, it’s because the repository is looking for /backup but it’s not mounted. (However /backups is). 

Classic 😅


For this case, it’s because the repository is looking for /backup but it’s not mounted. (However /backups is). 

Classic 😅

😂😂😂 so I was right, Veeam does not see the filesystem at all. But did not see the wrong mountpoint...


Interesting you get a file system message instead of a message commenting the path doesn’t exist!


Interesting you get a file system message instead of a message commenting the path doesn’t exist!

Yeah that is what we found odd.


Interesting you get a file system message instead of a message commenting the path doesn’t exist!

It sounds like the path /backup did exist, only the storage wasn't mounted to this mountpoint? So /backup indeed didn't use XFS but the filesystem from the OS root folder.


remember to set auto mount from crontab of repo is RDM LUN, if not at the next reboot the repo will not be mounted :P
In the procedure of deploy & configuration of a hardened repository you only give permissions to the directory mount point to a specific user for the mount of the XFS bck repo that does not have root privileges or sudoers.


Comment