Re: [OpenAFS] Re: afsd.fuse usage?

2011-09-20 Thread Troy Benjegerdes
Something is broken or not returning particularly useful error messages:

hozer@six:~$ /usr/sbin/afsd.fuse /tmp/afs
fuse: bad mount point `': No such file or directory
hozer@six:~$ /usr/sbin/afsd.fuse -- /tmp/afs
fuse: bad mount point `--': No such file or directory
hozer@six:~$ /usr/sbin/afsd.fuse -- -d /tmp/afs
fuse: bad mount point `-d': No such file or directory
hozer@six:~$ /usr/sbin/afsd.fuse -debug -- -d /tmp/afs
fuse: bad mount point `-d': No such file or directory

hozer@six:~$ dpkg -l openafs-fuse
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Description
+++-===-===-==
ii  openafs-fuse1.6.0-1 AFS distributed file system 
experimental FUSE client


On Thu, Sep 15, 2011 at 11:19:32PM -0500, Andrew Deason wrote:
 On Thu, 15 Sep 2011 21:22:08 -0500
 Troy Benjegerdes ho...@hozed.org wrote:
 
  I can't seem to find any documentation on afsd.fuse... Is there a
  HOWTO, or something? What works, what doesn't?
 
 It accepts all of the options that afsd does, and should behave in the
 same way. Give it a mountdir and a cachedir and it'll mount AFS in
 that dir and use the given cache directory.
 
 What should work is unauthenticated file access to AFS; everything else
 does not. So, you can't get authenticated access (unless you use host
 ACLs; but please don't use host ACLs), and you can't use any utilities
 like 'fs' with it.
 
 In developers terms, there's no pioctl, but anything that doesn't
 require a pioctl should work. We just haven't created a way to specify
 which cache manager do I communicate with?, so a pioctl call wouldn't
 know who to talk to.
 
 -- 
 Andrew Deason
 adea...@sinenomine.net
 
 ___
 OpenAFS-info mailing list
 OpenAFS-info@openafs.org
 https://lists.openafs.org/mailman/listinfo/openafs-info

-- 

Troy Benjegerdes 'da hozer'ho...@hozed.org  
7 elements Farm TerraCarbo biofuels

If you're going through hell, keep going. ~ Winston Churchill

The challenge in changing the world is not in having great ideas, it's in
having stupid simple ideas, as those are the ones that cause change.

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] Re: afsd.fuse usage?

2011-09-20 Thread Troy Benjegerdes
I have not set up fuse on this machine for regular user access, but I get the 
same behavior
on another machine that is configured.

hozer@six:~/cray/msgq$ sudo /usr/sbin/afsd.fuse -mountdir /tmp/afs/ -cachedir 
/tmp/vcache/ -d
[sudo] password for hozer: 
Sorry, try again.
[sudo] password for hozer: 
FUSE library version: 2.8.5
nullpath_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.16
flags=0x007b
max_readahead=0x0002
Starting AFS cache scan...found 0 non-empty cache files (0%).
afsd: All AFS daemons started.
Tue Sep 20 15:06:07 2011 Assertion failed! file 
/build/buildd-openafs_1.6.0-1-amd64-YBR2T1/openafs-1.6.0/src/afs/UKERNEL/afs_usrops.c,
 line 1284.



On Tue, Sep 20, 2011 at 02:58:33PM -0400, Matt W. Benjamin wrote:
 Hi Troy,
 
 When I just recently used fuse UKERNEL I did the following:
 
   afsd.fuse -memcache -mountdir /fafs -cachedir /vcache -d
 
 and got initial results.  I haven't worked much with it yet, but the cm 
 started and responded to vfsops.
 
 Matt
 
 - Troy Benjegerdes ho...@hozed.org wrote:
 
  Something is broken or not returning particularly useful error
  messages:
  
  hozer@six:~$ /usr/sbin/afsd.fuse /tmp/afs
  fuse: bad mount point `': No such file or directory
  hozer@six:~$ /usr/sbin/afsd.fuse -- /tmp/afs
  fuse: bad mount point `--': No such file or directory
  hozer@six:~$ /usr/sbin/afsd.fuse -- -d /tmp/afs
  fuse: bad mount point `-d': No such file or directory
  hozer@six:~$ /usr/sbin/afsd.fuse -debug -- -d /tmp/afs
  fuse: bad mount point `-d': No such file or directory
  
  hozer@six:~$ dpkg -l openafs-fuse
  Desired=Unknown/Install/Remove/Purge/Hold
  |
  Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion Description
  +++-===-===-==
  ii  openafs-fuse1.6.0-1 AFS distributed
  file system experimental FUSE client
  
  
  On Thu, Sep 15, 2011 at 11:19:32PM -0500, Andrew Deason wrote:
   On Thu, 15 Sep 2011 21:22:08 -0500
   Troy Benjegerdes ho...@hozed.org wrote:
   
I can't seem to find any documentation on afsd.fuse... Is there a
HOWTO, or something? What works, what doesn't?
   
   It accepts all of the options that afsd does, and should behave in
  the
   same way. Give it a mountdir and a cachedir and it'll mount AFS
  in
   that dir and use the given cache directory.
   
   What should work is unauthenticated file access to AFS; everything
  else
   does not. So, you can't get authenticated access (unless you use
  host
   ACLs; but please don't use host ACLs), and you can't use any
  utilities
   like 'fs' with it.
   
   In developers terms, there's no pioctl, but anything that doesn't
   require a pioctl should work. We just haven't created a way to
  specify
   which cache manager do I communicate with?, so a pioctl call
  wouldn't
   know who to talk to.
   
   -- 
   Andrew Deason
   adea...@sinenomine.net
   
   ___
   OpenAFS-info mailing list
   OpenAFS-info@openafs.org
   https://lists.openafs.org/mailman/listinfo/openafs-info
  
  -- 
  
  Troy Benjegerdes 'da hozer'   
  ho...@hozed.org  
  7 elements Farm TerraCarbo 
  biofuels
  
  If you're going through hell, keep going. ~ Winston Churchill
  
  The challenge in changing the world is not in having great ideas, it's
  in
  having stupid simple ideas, as those are the ones that cause change.
  
  ___
  OpenAFS-info mailing list
  OpenAFS-info@openafs.org
  https://lists.openafs.org/mailman/listinfo/openafs-info
 
 -- 
 
 Matt Benjamin
 
 The Linux Box
 206 South Fifth Ave. Suite 150
 Ann Arbor, MI  48104
 
 http://linuxbox.com
 
 tel. 734-761-4689
 fax. 734-769-8938
 cel. 734-216-5309

-- 

Troy Benjegerdes 'da hozer'ho...@hozed.org  
7 elements Farm TerraCarbo biofuels

If you're going through hell, keep going. ~ Winston Churchill

The challenge in changing the world is not in having great ideas, it's in
having stupid simple ideas, as those are the ones that cause change.

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] Re: afsd.fuse usage?

2011-09-20 Thread Matt W. Benjamin
Hi,

Dunno.  My fuse ukernel is pretty old, and worked.  From the src, afs_root() is 
failing.  Might be an issue with the supplied dirs?  I would at this point 
build with full debugging and trace into it.  

Matt


- Troy Benjegerdes ho...@hozed.org wrote:

 I have not set up fuse on this machine for regular user access, but I
 get the same behavior
 on another machine that is configured.
 
 hozer@six:~/cray/msgq$ sudo /usr/sbin/afsd.fuse -mountdir /tmp/afs/
 -cachedir /tmp/vcache/ -d
 [sudo] password for hozer: 
 Sorry, try again.
 [sudo] password for hozer: 
 FUSE library version: 2.8.5
 nullpath_ok: 0
 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
 INIT: 7.16
 flags=0x007b
 max_readahead=0x0002
 Starting AFS cache scan...found 0 non-empty cache files (0%).
 afsd: All AFS daemons started.
 Tue Sep 20 15:06:07 2011 Assertion failed! file
 /build/buildd-openafs_1.6.0-1-amd64-YBR2T1/openafs-1.6.0/src/afs/UKERNEL/afs_usrops.c,
 line 1284.
 
 
 
 On Tue, Sep 20, 2011 at 02:58:33PM -0400, Matt W. Benjamin wrote:
  Hi Troy,
  
  When I just recently used fuse UKERNEL I did the following:
  
afsd.fuse -memcache -mountdir /fafs -cachedir /vcache -d
  
  and got initial results.  I haven't worked much with it yet, but the
 cm started and responded to vfsops.
  
  Matt
  
  - Troy Benjegerdes ho...@hozed.org wrote:
  
   Something is broken or not returning particularly useful error
   messages:
   
   hozer@six:~$ /usr/sbin/afsd.fuse /tmp/afs
   fuse: bad mount point `': No such file or directory
   hozer@six:~$ /usr/sbin/afsd.fuse -- /tmp/afs
   fuse: bad mount point `--': No such file or directory
   hozer@six:~$ /usr/sbin/afsd.fuse -- -d /tmp/afs
   fuse: bad mount point `-d': No such file or directory
   hozer@six:~$ /usr/sbin/afsd.fuse -debug -- -d /tmp/afs
   fuse: bad mount point `-d': No such file or directory
   
   hozer@six:~$ dpkg -l openafs-fuse
   Desired=Unknown/Install/Remove/Purge/Hold
   |
  
 Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
   |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
   ||/ NameVersion Description
  
 +++-===-===-==
   ii  openafs-fuse1.6.0-1 AFS
 distributed
   file system experimental FUSE client
   
   
   On Thu, Sep 15, 2011 at 11:19:32PM -0500, Andrew Deason wrote:
On Thu, 15 Sep 2011 21:22:08 -0500
Troy Benjegerdes ho...@hozed.org wrote:

 I can't seem to find any documentation on afsd.fuse... Is
 there a
 HOWTO, or something? What works, what doesn't?

It accepts all of the options that afsd does, and should behave
 in
   the
same way. Give it a mountdir and a cachedir and it'll mount
 AFS
   in
that dir and use the given cache directory.

What should work is unauthenticated file access to AFS;
 everything
   else
does not. So, you can't get authenticated access (unless you
 use
   host
ACLs; but please don't use host ACLs), and you can't use any
   utilities
like 'fs' with it.

In developers terms, there's no pioctl, but anything that
 doesn't
require a pioctl should work. We just haven't created a way to
   specify
which cache manager do I communicate with?, so a pioctl call
   wouldn't
know who to talk to.

-- 
Andrew Deason
adea...@sinenomine.net

___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
   
   -- 
  
 
   Troy Benjegerdes 'da hozer'   
   ho...@hozed.org  
   7 elements Farm   TerraCarbo 
   biofuels
   
   If you're going through hell, keep going. ~ Winston Churchill
   
   The challenge in changing the world is not in having great ideas,
 it's
   in
   having stupid simple ideas, as those are the ones that cause
 change.
   
   ___
   OpenAFS-info mailing list
   OpenAFS-info@openafs.org
   https://lists.openafs.org/mailman/listinfo/openafs-info
  
  -- 
  
  Matt Benjamin
  
  The Linux Box
  206 South Fifth Ave. Suite 150
  Ann Arbor, MI  48104
  
  http://linuxbox.com
  
  tel. 734-761-4689
  fax. 734-769-8938
  cel. 734-216-5309
 
 -- 
 
 Troy Benjegerdes 'da hozer'   
 ho...@hozed.org  
 7 elements Farm   TerraCarbo 
 biofuels
 
 If you're going through hell, keep going. ~ Winston Churchill
 
 The challenge in changing the world is not in having great ideas, it's
 in
 having stupid simple ideas, as those are the ones that cause change.

-- 

Matt Benjamin

The Linux Box
206 

Re: [OpenAFS] Re: afsd.fuse usage?

2011-09-16 Thread Derrick Brashear
On Fri, Sep 16, 2011 at 12:19 AM, Andrew Deason adea...@sinenomine.net wrote:
 On Thu, 15 Sep 2011 21:22:08 -0500
 Troy Benjegerdes ho...@hozed.org wrote:

 I can't seem to find any documentation on afsd.fuse... Is there a
 HOWTO, or something? What works, what doesn't?

 It accepts all of the options that afsd does, and should behave in the
 same way. Give it a mountdir and a cachedir and it'll mount AFS in
 that dir and use the given cache directory.

 What should work is unauthenticated file access to AFS; everything else
 does not. So, you can't get authenticated access (unless you use host
 ACLs; but please don't use host ACLs), and you can't use any utilities
 like 'fs' with it.

 In developers terms, there's no pioctl, but anything that doesn't
 require a pioctl should work. We just haven't created a way to specify
 which cache manager do I communicate with?, so a pioctl call wouldn't
 know who to talk to.

sick idea: use the rmtsysd interface to do it, since we already have tools that
support it (all of them).



-- 
Derrick
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info


Re: [OpenAFS] Re: afsd.fuse usage?

2011-09-16 Thread Derrick Brashear
On Fri, Sep 16, 2011 at 11:14 AM, Andrew Deason adea...@sinenomine.net wrote:
 On Fri, 16 Sep 2011 08:29:26 -0400
 Derrick Brashear sha...@gmail.com wrote:

 sick idea: use the rmtsysd interface to do it, since we already have
 tools that support it (all of them).

 Yeahbut, I mean, how do you specify which client to talk to? There could
 be several on the machine. I don't think straight rmtsys would work
 because of that, but I guess the same AFSSERVER mechanism could be used
 to specify? Like, have a syntax that instead says talk to the cm
 mounted at X instead of a host name. From there I was thinking
 communicating using xattrs, but I don't know.

we could add alternate port support for rmtsys, and then you have a
virtual file in the top of the mounted (fuse) afs, which specifies
localhost:port

export AFSSERVER=`cat /path/to/my/afs/.AFSSERVER`

and then just do stuff.

the xattrs method is not a bad idea either, i wish the GSoC project along those
lines had gotten on further.

 --
 Andrew Deason
 adea...@sinenomine.net

 ___
 OpenAFS-info mailing list
 OpenAFS-info@openafs.org
 https://lists.openafs.org/mailman/listinfo/openafs-info




-- 
Derrick
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info