maindavfs2 - Support: sr #108951, Cannot create a directory called...

 
 

sr #108951: Cannot create a directory called '0', mkdir fails.

Submitter:  None
Submitted:  Sun 10 Jan 2016 08:34:48 AM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  _71007
Originator Email:  -email is unavailable- Open/Closed:  Closed
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 13 Jan 2016 04:45:27 PM UTC, comment #11: 

Nice to hear that the problem has been resolved quickly.

"Is it best to use fuse?"
Currently it makes no difference (at least none that would be noticed). But davfs2 will probably drop coda support some day.

Werner

- <_71007>
Tue 12 Jan 2016 08:39:54 PM UTC, comment #10: 

Hello,

The issue is now resolved. My webdav provider has patched the problem. Looks like it was some sort of addressing issue on their end.

Anonymous
Mon 11 Jan 2016 07:13:03 PM UTC, comment #9: 

I can confirm that box.com works for me.

Anonymous
Mon 11 Jan 2016 06:46:12 PM UTC, comment #8: 

The only reason that I have coda, was to test if the problem was related to fuse or not. I just haven't switched it back yet. There is no technical reason, the error I'm getting happens with both. Is it best to use fuse?

Anonymous
Mon 11 Jan 2016 06:40:54 PM UTC, comment #7: 

From your log files I see that you use the coda kernel file system. I intend to drop coda support some time in the future and to only support fuse. Is there a reason why you prefer to or even need to use coda and not fuse?

This is not related to the problem with directory 0. But it would be important for the development of davfs2 to know whether there is still need for coda. Dropping coda support would reduce code complexity and even allow for better support for file times.

Werner

- <_71007>
Mon 11 Jan 2016 06:10:33 PM UTC, comment #6: 

Yes, I've tried creating it in a subfolder. It didn't work. I can, however, create a file called 0, just not a folder. I also tried on a different provider "cloudme" and got the same error. I'll try on box.com and see what happens.

Thanks

Anonymous
Mon 11 Jan 2016 06:05:38 PM UTC, comment #5: 

The log file shows that there is indeed no message body included. The headers concerning content-type and transfer-encoding are just for fun.

I have tested creating a directory named "0" with the following WebDAV-Servers:

The one provided by my ISP
https://sd2dav.1und1.de

box.com
https://dav.box.com/dav

and BSCW
http://public.bscw.de/bscw/nj_bscw.cgi

The dreation of directory 0 was successful with all of them.

I reckon it is something special with the OpdenDrive server software. Maybe they use that directory for internal purposes.

Did you try to create a directory named "0" in some subdirectory instead within the root directory, e.g. /test/0/ ?

Werner

- <_71007>
Mon 11 Jan 2016 04:10:11 PM UTC, comment #4: 

I suspected the same thing. I opened a ticket yesterday with opendrive to see what's going on. I haven't heard anything back yet. I also tested mounting the webdav in Windows and found the same problem. So I'm definitely suspecting a problem on the webdav side. That being said, I tried another provider and found the same thing. Which provider do you use that's working for you?

I've attached a new syslog file with the added logging. I don't see anything helpful, but I suspect that you're more familiar with what to look for then I am.

Thanks again.

Anonymous
Mon 11 Jan 2016 10:33:46 AM UTC, comment #3: 

In your debug log I found these lines:

347: Sending request headers:#012MKCOL /0/ ...

350: [status-line] < HTTP/1.1 403 Forbidden

355: [hdr] Content-Type: text/html; charset=UTF-8

357: [hdr] Transfer-Encoding: chunked

371: Got chunk size: 0

Most important: the server returns "403 Forbidden" in response to the request to create directory "0". So it definitely is a restriction set by the server.

It also announces a body of type text/html in chunked transfer encoding. This body should contain the reason for 403 Forbidden. But this body seems to be empty (chunk size: 0).

You should contact the server's support desk to ask for the reason and whether the restriction can be removed.

You might first check whether there really is no body. To do this you should additionally add option "debug httpbody" to your davfs2.conf file. The amount of debug messages will get much bigger. If there is a message body it would be somewhere between the request line ("MCOL /0/ ...") and the line "Request ends, status 403 ...".

Whether you are not succesful or not, please inform me about your findings.

Werner

- <_71007>
Sun 10 Jan 2016 09:03:49 PM UTC, comment #2: 

Thanks for looking at this so quickly. I've followed your instructions and attached the syslog file.

Anonymous
Sun 10 Jan 2016 04:17:28 PM UTC, comment #1: 

There is no problem creating a directory named "0" on my Debian 8 system. It might be a restriction on the server side, or something else.

Please do this:

  • add option "debug most" to your davfs2.conf file
  • mount the file system
  • try to create a directory named "0" and wait until it returns with an error
  • unmount the file system
  • get the debug messages from mount.davfs and attach them to your next message (the debug messages will be in /var/log/syslog as well as in /var/log/debug and /var/log/daemon.log. Take any.)


Please restrict your file system actions to this one command in order to keep the number of debug messages small.

Werner

- <_71007>
Sun 10 Jan 2016 08:34:48 AM UTC, original submission:  

Hello,

I'm running debian 8 linux, with davfs2 1.5.2. For some reason, I cannot create a directory named "0". I can create one called "00" or any other number, just not zero. Normally this wouldn't be a problem and I'd just pick another name, but all of the backup software that I'm testing tries to create a folder "0" and fails. Please let me know if there is any more information that I need to provide or if I can help in anyway to fix this.

Thanks
Chris

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

Attached Files
file #35992:  syslog added by None (37KiB - application/octet-stream)
file #35977:  syslog.davfs added by None (29KiB - application/octet-stream - I've attached a trimmed copy of syslog following your instructions.)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by _71007 (Posted a comment)
  • -email is unavailable- added by None (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 6 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-04-15 _71007 Open/ClosedOpen Closed
    2016-01-13 _71007 StatusIn Progress Done
    2016-01-11 None Attached File- Added syslog, #35992
    2016-01-10 None Attached File- Added syslog.davfs, #35977
    2016-01-10 _71007 StatusNone In Progress
        Assigned toNone _71007

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code