Server leaves spurious .meta files with a content-length triple

[timbl]

Environment

$ community-solid-server --version
7.0.3
$ node --version
v18.19.0

Description

Running with the file backend, I find that .meta files have started to appear on some not all of the data files that the server handles. Not obvious which files get them and why.

For example

$ ls -l Data/.../TEQU4BT4L-U049J62J1LK-9b3*
-rw-r--r--  1  120173 Oct  4  2023 Data/.../TEQU4BT4L-U049J62J1LK-9b35ce73d1f0-512.jpg
-rw-r--r--  1      188 Oct  4  2023 Data/.../TEQU4BT4L-U049J62J1LK-9b35ce73d1f0-512.jpg.meta

Where the content of the .meta file is as below

$ cat Data/.../TEQU4BT4L-U049J62J1LK-9b35ce73d1f0-512.jpg.meta
<https://timbl.com/timbl/Data/Contacts/Person/f472487e-4c2e-498c-a4dc-..-512.jpg> <http://www.w3.org/2011/http-headers#content-length> 120173.
$

There should be no .meta files in my the server data at all.

I don't want them cluttering up the file space

[joachimvh]

There is indeed no reason to store the content-length in the metadata in most cases so we could remove it.

Note that this will only happen when you are running a server where quota limits on pods are enabled. If quotas are disabled those metadata files will not be generated.