filename/paths with spaces with mounted fs

Asked by RobM

Hello, I'm trying to access storage hosted by Cubby through their webdav interface.

I can use the nautilus interface via the "connect to server" option. I enter davs://webdav.cubby.com and then enter my login/pw. All is good and all my remote files can be browsed. Many of the paths within this share have names that include whitespace (eg: "Robs folder 1").

BUT when I try to mount the remote files using instructions similar to:https://doc.owncloud.org/server/6.0/user_manual/files/files.html (modify for the Cubby-specific stuff) I can mount the remote share, but ONLY the paths that do not include whitespace are visible in the mounted path.

If I try to mount similar to: mount.davfs https://webdav.cubby.com ~/cubby the mount succeeds, but with the whitespace problem. If I try: mount.davfs davs://webdav.cubby.com ~/cubby this never works.

I saw some old posts about a neon patch that dealt with whitespace, but this mostly seemed to address whitespace in the name of the webdav server, not the paths of files/folders within the server.

Just to be clear, the whitespace that I'm referring to is not in the path or URL of the networked resource. This is not a problem estabishing the mount. I can mount the resource.

Rather, the whitespace is in the names of the individual folders/files within the networked resource. The mounted tree does not show the files/folders that have whitespace in their names. There are tens of thousands of files within that directory tree, and the directory tree is shared among my other machines. Renaming all of the files/folders that have whitespace is one option, but it's a bad one since this would break other dependencies in my system.

So, my question remains: why is it that the folders with whitespace are visible when viewed through nautilus' connect to server option, but not when they are mounted?

Do webdav servers accessed via davs:// and https:// have different whitespace behavior? (It seems so.)

I'm using 14.04LTS and davfs2 1.4.7-3.

Thanks - Rob

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu davfs2 Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

You will need to escape the spaces. Like this:

Robs\ folder\ 1

And the spaces will be read as whitespace rather than a separator for operands in the mount.

Revision history for this message
RobM (maccurdy) said :
#2

Hi, thanks for the response.

Just to be clear, the whitespace that I'm referring to is not in the path or URL of the networked resource. This is not a problem estabishing the mount. I can mount the resource.

Rather, the whitespace is in the names of the individual folders/files within the networked resource. The mounted tree does not show the files/folders that have whitespace in their names. There are tens of thousands of files within that directory tree, and the directory tree is shared among my other machines. Renaming all of the files/folders that have whitespace is one option, but it's a bad one since this would break other dependencies in my system.

So, my question remains: why is it that the folders with whitespace are visible when viewed through nautilus' connect to server option, but not when they are mounted?

Revision history for this message
Launchpad Janitor (janitor) said :
#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
RobM (maccurdy) said :
#4

Hello, does anyone know the answer to this question? I'm wondering if this is a bug?

Revision history for this message
Launchpad Janitor (janitor) said :
#5

This question was expired because it remained in the 'Open' state without activity for the last 15 days.