[SOLVED] 400 Bad Request [...] unable to detect file type

[ojaksch]

Full error message is

proxmox-backup-proxy[3744]: GET /api2/json/admin/datastore/vms/snapshots: 400 Bad Request: [client [::ffff:IPADDRESS]:35470] unable to detect file type

Are there any special requirements for PBS? I'm playing around with it's setup on different hardware constellations, but sometimes getting mentioned error when accessing Datastore/[datastore]/Content.

I did my first setup of PBS by iso image. Everything is working great. Very satisfying.

The 2nd setup was on top of an actual PVE, which exists since some years. No ZFS involved as server runs a caching disk controller. Data space for PBS was a single bare 2TB harddisk. Doing backups to the defined datastore is working, but when showing it's content by GUI it throws the mentioned error.
I then deleted the disk, created a simple LVM/xfs on it, recreated the datastores on it and error is gone. All is working, all is good.

The 3rd setup was another, different server, similar to the 2nd one, two big disks w/ RAID1, no caching disk controller but no ZFS (old but well maintained setup of PVE). Data space for PBS is already a LVM/xfs, doing backups to the defined datastore is working, but when showing it's content by GUI it throws the mentioned error.

What I'm missing? Or what I'm doing wrong?

 

[fabian]

possibly your XFS file systems were created with ftype=0 (you can check with xfs_info)?

 

[fabian]

https://bugzilla.proxmox.com/show_bug.cgi?id=2915

 

[ojaksch]

possibly your XFS file systems were created with ftype=0 (you can check with xfs_info)?

This could (should!) be the "issue". The server was setup in 2012 and the xfs_info throws ftype=0, which was the default at the time in mkfs.xfs, if I remember correctly.
Will dump, recreate and restore it's data the next nights or coming weekend as server is in use during the day.
Anyway, thanks for the hint, will report back!

 

[ojaksch]

possibly your XFS file systems were created with ftype=0 (you can check with xfs_info)?

Was definitely the issue. I cleared out and dumped all data last night (using the instructions from https://superuser.com/questions/1321926/recreating-an-xfs-file-system-with-ftype-1#), reformatted the logical volume, ensured that it's using ftype=1 and voila, error message is gone.
Great, and again thanks for the hint!