incorrect size information

This is still unchanged as of today. I would appreciate some help in triaging this. I only seem to experience this with strato.de so I wonder if they are supplying incorrect information somehow.

I believe this is caused by the hoster not implementing quota-available-bytes and quota-used-bytes as defined in RFC 4331 (www.ietf.org/rfc/rfc4331.txt). Nonetheless, even if this is the case, davfs2 should not return some fantasy value.

Here is the information I collected with cadaver from two hosters. The first one is Strato and does not return a value for above variables while the second one does. The second hoster is also showing correctly in df.

Strato as dav host:
dav:/users/XYZ/> propget .
Fetching properties for `.':
DAV: resourcetype = <DAV:collection></DAV:collection>
DAV: creationdate = 2015-03-05T06:27:07Z
DAV: getlastmodified = Thu, 05 Mar 2015 06:27:07 GMT
DAV: getetag = "a-b-51084a83426d1"
DAV: supportedlock =
<DAV:lockentry>
<DAV:lockscope><DAV:exclusive></DAV:exclusive></DAV:lockscope>
<DAV:locktype><DAV:write></DAV:write></DAV:locktype>
</DAV:lockentry>
<DAV:lockentry>
<DAV:lockscope><DAV:shared></DAV:shared></DAV:lockscope>
<DAV:locktype><DAV:write></DAV:write></DAV:locktype>
</DAV:lockentry>

DAV: lockdiscovery =

Other dav hoster:
dav:/> propget .
Fetching properties for `.':
http://webdav.org/cadaver/custom-properties/ imageheight = unknown
http://webdav.org/cadaver/custom-properties/ thumbnailuri = unknown
http://webdav.org/cadaver/custom-properties/ imagewidth = unknown
DAV: supportedlock =
<DAV:lockentry>
<DAV:lockscope><DAV:exclusive></DAV:exclusive></DAV:lockscope>
<DAV:locktype><DAV:write></DAV:write></DAV:locktype>
</DAV:lockentry>

DAV: iscollection = TRUE
DAV: resourcetype =
<DAV:collection></DAV:collection>
DAV: creationdate = Thu, 05 Mar 2015 15:06:11 GMT
DAV: lockdiscovery =

DAV: quota-used-bytes = 490387428
DAV: isreadonly = FALSE
DAV: quota-available-bytes = 26353158172
DAV: getcontenttype = text/html; charset=utf-8
DAV: name =
DAV: getcontentlength = 0
DAV: getlastmodified = Thu, 05 Mar 2015 15:06:11 GMT
DAV: getcreated = Thu, 05 Mar 2015 15:06:11 GMT
DAV: getetag = "0-0-0-1425567971028"
DAV: displayname =

Status changed to 'Confirmed' because the bug affects multiple users.

The same here:
➜ ~ df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 8090936 0 8090936 0% /dev
tmpfs 1624240 1696 1622544 1% /run
/dev/sda2 61256516 9482760 48632380 17% /
tmpfs 8121196 57768 8063428 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 8121196 0 8121196 0% /sys/fs/cgroup
/dev/loop0 2432 2432 0 100% /snap/gnome-calculator/180
/dev/loop1 89088 89088 0 100% /snap/core/4917
/dev/loop3 144384 144384 0 100% /snap/gnome-3-26-1604/70
/dev/loop2 14848 14848 0 100% /snap/gnome-logs/37
/dev/loop4 13312 13312 0 100% /snap/gnome-characters/103
/dev/loop5 3840 3840 0 100% /snap/gnome-system-monitor/51
/dev/loop6 35584 35584 0 100% /snap/gtk-common-themes/319
/dev/sda1 47371 6197 41174 14% /boot/efi
/dev/sda4 180590952 146340224 25054184 86% /home
http://vidcloud.myqnapcloud.com/NAS 1333333332 800000000 533333332 61% /media/vid/NAS
tmpfs 1624236 132 1624104 1% /run/user/1000

I don't see the weird case from my side as I'm using focal to verify. I'd like to set this as invalid, and of course please file an bug if someone can reproduce again.

> I don't see the weird case from my side as I'm using focal to verify. I'd like to set this as
> invalid, and of course please file an bug if someone can reproduce again.

Woodrow, stop this rubbish right now. You are working for Canonical and should really understand a lot better how bug triage works. As long as you do NOT, please stop closing tickets left and right. Your "contributions" are hurtful!