#16 Leading and trailing spaces on file names are ignored

[ngamradt]

Hello,

We have a large number of Mac users at our company. The crappy Mac Finder allows for leading and trailing spaces to be added to file names. It appears that curlftpfs is stripping off all leading and trailing spaces. This causes a huge issue for me because I am trying to use curlftpfs to back up a large amount of data that was created by Mac users. When curlftpfs tries to get a file that has a leading space, it trying to grab a file that doesn't have a leading space and thus gets an error.

FuseFTP doesn't have this issue, but it has many other different issues that make it completely impractical.

I had reported an earlier bug about percent signs, I am not not sure if the issue was with percent signs, or if that file had a space in front of it (I ended up deleting that file because it was a trivial file).

Anyway, if the issue with leading and trailing spaces could be resolved, it would be of huge help to me with my current problem. Curlftpfs is so fast at transferring files, it would be great if I could use it.

Anyway, thanks again for the great product!

Sincerely,

Neal Gamradt

[Robson Braga Araujo]

Logged In: YES
user_id=307089
Originator: NO

Hi,

I think this issue is already solved in the current version that is not yet released. Can you test it? You can grab it from the sourceforge CVS or from googlecode's svn server:
svn checkout http://curlftpfs.googlecode.com/svn/trunk/ curlftpfs

Plase, see if both this whitespace issue and the percentage sign issue are solved with the newest version.

[ngamradt]

Logged In: YES
user_id=1686774
Originator: YES

Hello,

I use Subversion so I was able to easily check out the trunk from the site you listed. However, I have a question. The version that I checked out doesn't have a "configure" script for me to run.

I am wondering if I am just supposed to copy and paste the files from the SVN trunk into the curlftpfs-0.9 folder that I already have and re-run the install process, or if there was supposed to be a "configure" script after I checked out the SVN trunk.

Please let me know what I am missing so that I can compile and test from the SVN trunk. I am excited because if this works it could solve some problems. Thanks again!

Sincerely,

Neal Gamradt

[ngamradt]

Logged In: YES
user_id=1686774
Originator: YES

Hello,

I took the files from the SVN trunk and copied them over the files in the curlftpfs-0.9 folder. I then re-ran the whole install process. The final file installed in /usr/local/bin was a different size so it appears this process worked. Please let me know if there is something I should have done differently.

Anyway, I experimented with the newly compiled version. So far it appears that it has solved the issue because when I do a directory listing it was now correctly displaying a file that had a leading space. I am going to test it now on a real backup and I will let you know what happens.

Thanks again for this tool!

Sincerely,

Neal Gamradt

[Robson Braga Araujo]

Logged In: YES
user_id=307089
Originator: NO

Sorry about that. The way you solved the problem should work too.

The configure script is generated automatically. You have to run:
$ autoreconf -fi
That should take care of it. If you don't have autoreconf, try running: autoheader, autoconf and automake, but I don't remember the right order. I hope that helps.

Please, also confirm if this solves the percent sign problem. If it does, I'm going to close both bugs.

[ngamradt]

Logged In: YES
user_id=1686774
Originator: YES

Hello,

Thanks for the information on autoreconf. Over the course of the night I received a number of errors from the backup system. I have not yet had time to check into if they are issues with spaces or if the errors are something else. I will let you know what I find out.

Neal

[ngamradt]

Logged In: YES
user_id=1686774
Originator: YES

Hello,

Here is what I have found out so far, two of the files gave "ERR=Input/output error" as their error. One file was 10GB and the other file was 15GB, they were MOV files from one of our video guys. I don't see any issues with the permissions and I know the connection to this server is stable, so I assume that this might have something to do with the size of the files. Any thoughts on this?

The other permissions errors were caused by more Apple Finder files. There are a bunch of "._Icon" files that are getting permissions errors. Upon further examination, there is a character that curlftpfs doesn't see, when I copy and paste the name of these files into VIM, they appear as "._Icon^M". So it appears that there is an actual line ending in the file name (or whatever "^M" stands for). I have no idea how my co-workers do things like this, but it appears to be all over the place. Do you want me to put in a different bug report for this?

After doing some testing, it appears that the percentage sign issue has been solved as well as the issues with with spaces. Thanks for fixing these two issues. Unfortunately, the two new ones above are just adding to the list.

Neal

[Robson Braga Araujo]

Logged In: YES
user_id=307089
Originator: NO

CurlFtpFS shouldn't have a problem with file sizes. Are these the only files bigger than 2GB that you tried to transfer? Are you sure that your filesystem supports files bigger than that?

Some FTP servers always give permission errors for files that start with a dot. Are you sure that the files contain a "^M" character? I'm not sure if this is possible.

I'll close both bugs then. If you you are sure that you can reproduce these other bugs, please open new ones with instructions. Thanks a lot for using the program and giving feedback.