Loading Profile...
2.0, empty directories
In addition to being slow, I change to a directory and it never shows any files.
I’m frustrated
7
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The best solution from the company
-
We’re really sorry about this empty directory problem. We’re working hard to fix it, but at this point we’ve still been unable to replicate the issue.
The fastest way for us to solve this problem would be if someone who is experiencing it could share with us a temporary login to their server. We are, of course, very careful with other people’s server information, and won’t use it for anything except careful testing.
In the meantime, anyone who wishes to use ExpanDrive 1.3.4 can download it here:
http://download.expandrive.com/1.3.4/...
I’m hopeful
The company says
this solves the problem
-
Inappropriate?Here is log info.
4/25/09 12:55:00 AM ExpanDrive[305] EXPANDRIVE_AUTH_PASSWORD:
4/25/09 12:55:00 AM ExpanDrive[305] EXPANDRIVE_MKDIR_MOUNTPOINT:/Volumes/KIERASKY.COM
EXPANDRIVE_CONNECT_PROGRESS:drive_connected
EXPANDRIVE_GET_CONFIG:volicon_path
4/25/09 12:55:02 AM ExpanDrive[305] .sdef error: (null)
4/25/09 12:55:02 AM ExpanDrive[305] line number: 2
4/25/09 12:55:02 AM ExpanDrive[305] .sdef error: (null)
4/25/09 12:55:02 AM ExpanDrive[305] line number: 2
4/25/09 12:55:04 AM Path Finder[174] -[NTFolderWatcher FSEventStreamCreate] FSEventStreamCreate failed: /Volumes/KIERASKY.COM
4/25/09 12:55:04 AM Path Finder[174] -[NTFolderWatcher FSEventStreamCreate] FSEventStreamCreate failed: /Volumes/KIERASKY.COM
4/25/09 12:55:04 AM Path Finder[174] -[NTFolderWatcher FSEventStreamCreate] FSEventStreamCreate failed: /Volumes/KIERASKY.COM
4/25/09 12:55:06 AM Path Finder[174] -[NTFolderWatcher FSEventStreamCreate] FSEventStreamCreate failed: /Volumes/KIERASKY.COM/images
4/25/09 12:55:18 AM Path Finder[174] -[NTFolderWatcher FSEventStreamCreate] FSEventStreamCreate failed: /Volumes/KIERASKY.COM/images
4/25/09 12:55:04 AM [0x0-0x19019].com.cocoatech.PathFinder[174] 2009-04-25 00:55 Path Finder[174] (CarbonCore.framework) FSEventStreamCreateRelativeToDevice(): failed assertion 'deviceToWatch > 0'
4/25/09 12:55:04 AM [0x0-0x19019].com.cocoatech.PathFinder[174] 2009-04-25 00:55 Path Finder[174] (CarbonCore.framework) FSEventStreamCreateRelativeToDevice(): failed assertion 'deviceToWatch > 0'
4/25/09 12:55:04 AM [0x0-0x19019].com.cocoatech.PathFinder[174] 2009-04-25 00:55 Path Finder[174] (CarbonCore.framework) FSEventStreamCreateRelativeToDevice(): failed assertion 'deviceToWatch > 0'
4/25/09 12:55:06 AM [0x0-0x19019].com.cocoatech.PathFinder[174] 2009-04-25 00:55 Path Finder[174] (CarbonCore.framework) FSEventStreamCreateRelativeToDevice(): failed assertion 'deviceToWatch > 0'
4/25/09 12:55:18 AM [0x0-0x19019].com.cocoatech.PathFinder[174] 2009-04-25 00:55 Path Finder[174] (CarbonCore.framework) FSEventStreamCreateRelativeToDevice(): failed assertion 'deviceToWatch > 0'
4/25/09 12:56:05 AM Path Finder[174] -[NTFolderWatcher FSEventStreamCreate] FSEventStreamCreate failed: /Volumes/KIERASKY.COM/images/gallery_thms
4/25/09 12:56:05 AM [0x0-0x19019].com.cocoatech.PathFinder[174] 2009-04-25 00:56 Path Finder[174] (CarbonCore.framework) FSEventStreamCreateRelativeToDevice(): failed assertion 'deviceToWatch > 0'
I’m frustrated
-
-
Inappropriate?Hi, Peedy -- I'm sorry for the troubles. Does this problem occur for any directory you attempt to view, or only for certain directories? Are you connecting with SFTP or with FTP?
I notice from the log you quoted that you seem to be using PathFinder; are you able to see the contents of directories using the Finder or in the Terminal, for example by running the command "ls /Volumes/YourDrive/FolderName" with appropriate substitutions? -
Inappropriate?It really kind of weird because it seems to work fine UNTIL after I go into a directory. So for example I go into a subdir and then try to backout and go into another subdir and everything starts to be blank and unresponding.
I am using SFTP, and yes using PathFinder but I also tried in Finder and the same thing happens. I didn't try the Terminal however. At this point I had to go back to 1.3.4 because I couldn't get any work done with the state of 2.0, and right about now I am not liking that I paid to upgrade and the product bombed (at least it is for me), the first time I went to use it.
At this point I cannot mess with 2.0 until its fixed. At least not on this Mac, I do have another mac I can install it on and see if it does the same thing.
I’m frustrated
-
Inappropriate?We’re really sorry about this empty directory problem. We’re working hard to fix it, but at this point we’ve still been unable to replicate the issue.
The fastest way for us to solve this problem would be if someone who is experiencing it could share with us a temporary login to their server. We are, of course, very careful with other people’s server information, and won’t use it for anything except careful testing.
In the meantime, anyone who wishes to use ExpanDrive 1.3.4 can download it here:
http://download.expandrive.com/1.3.4/...
I’m hopeful
The company says
this solves the problem
-
Inappropriate?I'm not sure it's a server issue??? It works fine on one of my machines but not on the other! Something on the machine??? not the server?
I’m curious
-
Inappropriate?I don't think it has anything to do with the server at all. Otherwise why would 1.3.4 work just fine? In fact they both rely on MacFuse so its not a problem with fuse either. So its something specific in the Expandrive 2.0 code changes apparently. I am gonna install it on my other mac and see how it does on there.
1 Comment Add a comment
This solves the problem
-
ExpanDrive 2.0 is a complete rewrite of our SFTP communication layer, and there are a number of things it handles differently from ExpanDrive 1.3.4 that could explain the difference. More to the point, we need to reproduce the problem before we can solve it, and the fastest way to reproduce it is to replicate a situation where it’s already been seen. In this case, that means connecting to a setup that has an ‘empty’ folder. -
Inappropriate?I will be happy to provide you access to my server however I need some way to securely transfer the information to you.1 Comment Add a comment
This solves the problem
-
That would be awesome. If you email support@expandrive.com we can setup a secure communication channel that meets your needs.
-
Inappropriate?FYI to everyone having this problem. I got mine to work. Here's how I did it: While ExpanDrive 2.0 was trying to find what was in a folder, I did a Force Quit of the Finder. Then I quit ExpanDrive 2.0. On restart, clicking on a non-empty folder got the folder contents.
I’m intrigued
2 Comments Add a comment
This solves the problem
-
Haven't tried this but even so its hardly a fix.
-
Certainly not what you paid $ for, but hopefully it gets you working until the root issue is corrected by the ExpanDrive team.
EMPLOYEE
EMPLOYEE
