Re: [Pharo-users] Filesystem bug or limitation?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] Filesystem bug or limitation?

Ben Coman
 
Juan Ignacio Vaccarezza wrote:

> Hello all,
>     I'm playing with pharo filesystem and I run into an issue.
>    
>     I want to access the content of a remote windows folder from
> Linux, so my idea was  to mount it using mount -t cifs, which works
> perfect, following that i thought I will access from pharo as any
> other directory.
>     Instead of that if I try to make a fileReference with the mount
> point path I't says it deos not exists. But if I ask the parent folder
> for its childrends the mount point appears but not as a directory.
>
> Example:
> given:
>         /mnt/remoteFolderMountPoint
>
> before mounting:
>         '/mnt/remoteFolderMountPoint' asFileReference exists -> true
>         '/mnt/remoteFolderMountPoint' asFileReference isDirectory -> true
> after mounting
>         '/mnt/remoteFolderMountPoint' asFileReference exists -> false
>         '/mnt/remoteFolderMountPoint' asFileReference isDirectory -> false
>      
>       Other curious thing is that if I do: '/mnt/' asFileReference
> children, it shows the mountpoint forlder that claims not to exist :S
>
> Any ideas?
>
> Thanks,
> Juan
>

 From http://php.net/manual/en/function.is-dir.php...
Just a note for anyone who encounters is_dir() returning false on CIFS
mount points or directories within those mount points on 2.6.31 and
newer kernels: Apparently in new kernels they've started using the CIFS
serverino option by default.  With Windows shares this causes huge inode
numbers and which apparently can cause is_dir() to return false.  Adding
the noserverino option to the CIFS mount will prevent this.  This may
only occur on 32 systems but I don't have a 64 bit install to test against.

So try using "noserverino" and testing before and after with " ls -i "

Alternatively maybe compiling the VM with -D_FILE_OFFSET_BITS=64 would work
https://bugzilla.samba.org/show_bug.cgi?id=7707

Also
http://stackoverflow.com/questions/7600863/inode-of-directory-on-mounted-share-changes-despite-no-change-in-modification-ti
https://lists.samba.org/archive/samba-technical/2010-December/075074.html

HTH,
cheers -ben