incorrect size information
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | davfs2 (Ubuntu) |
Undecided
|
Unassigned | ||
Bug Description
I mounted an online hard disk from strato.de via davfs. The provider allows me 150G of storage of which less than 1G is used. "df -h" returns some funny numbers that have no resemblence to reality.
$ df -h|grep strato
https:/
| tags: | added: trusty |
| Rolf Leggewie (r0lf) wrote : | #1 |
| Rolf Leggewie (r0lf) wrote : | #2 |
I believe this is caused by the hoster not implementing quota-available
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: creationdate = 2015-03-
DAV: getlastmodified = Thu, 05 Mar 2015 06:27:07 GMT
DAV: getetag = "a-b-51084a83426d1"
DAV: supportedlock =
<DAV:lockentry>
<DAV:lockscope>
<DAV:locktype>
</DAV:lockentry>
<DAV:lockentry>
<DAV:lockscope>
<DAV:locktype>
</DAV:lockentry>
DAV: lockdiscovery =
Other dav hoster:
dav:/> propget .
Fetching properties for `.':
http://
http://
http://
DAV: supportedlock =
<DAV:lockentry>
<DAV:lockscope>
<DAV:locktype>
</DAV:lockentry>
DAV: iscollection = TRUE
DAV: resourcetype =
<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
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-
DAV: displayname =
| Launchpad Janitor (janitor) wrote : | #3 |
Status changed to 'Confirmed' because the bug affects multiple users.
| Changed in davfs2 (Ubuntu): | |
| status: | New → Confirmed |


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.