Re: [MooseFS-Users] cannot retrieve current directory .. getcwd not working on mounted moosefs filesystem

[Krzysztof K. <krz...@mo...>]

Hi Matt,

Thank you for your submission. We confirm that the problem exists in 
Ubuntu 15.04 with MooseFS 2.0.76. It's connected with mechanism for 
reusing inodes that was changed in MooseFS 2.0.74 to use kernel FORGET 
functionality. Both version 2.0.74 and 2.0.76 were tested on Ubuntu LTS 
editions and worked fine.

Unfortunately the new kernel in Ubuntu 15.04 changed ABI for working 
with FORGET's for inodes. With this new ABI kernel does not even send 
any request to mfsmount when invoking the syscall GETCWD.

Quick fix might be to execute script as follows:

[ ~]$ cat test.rb
#!/bin/env ruby
puts Dir.pwd
[ ~]$ cd ; ./test.rb
/home/mfs

In this situation the "cd" command before actual script executes LOOKUP 
syscall for current directory and next GETCWD syscall - that usually is 
invoked in the beginning of the script - works fine.

Anyway we'll start working on this problem and solve it in the next 
version of MooseFS.

Best Regards,
Krzysztof Kielak
Director of Operations and Customer Support


W dniu 2015-09-25 05:58, Matt Welland napisał(a):
> I'm on Ubuntu 15.04 using moose 2.0.76. I have a master + chunk server
> running on a Ubuntu 14.10 machine and moosefs is mounted on that
> machine without problems. On the 15.04 machine the getcwd call seems
> to be failing completely. Note that ls, cat, vi and other commands all
> work fine.
> 
> Examples:
> 
> 1. Fossil can't see the current directory
> $ fossil status
> cannot find current working directory; No such file or directory
> 
> 2. Ruby call to getcwd fails
> 
> $ irb
> irb(main):001:0> Dir.pwd
> Errno::ENOENT: No such file or directory - getcwd
>     from (irb):1:in `pwd'
>     from (irb):1
>     from /usr/bin/irb:11:in `<main>'
> 
> 3. Chicken scheme call to getcwd fails
> csi> (current-directory)
> 
> Error: (current-directory) cannot retrieve current directory
> 
>     Call history:
> 
>     <syntax>      (current-directory)
>     <eval>      (current-directory)    <--
> 
> this was working fine up until a few days ago, I think a recent
> apt-get update;apt-get upgrade might have coincided with it breaking.
> I haven't changed any configurations. Any help fixing this
> appreciated.
> 
> 
> ------------------------------------------------------------------------------
> 
> _________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users