[7734] in testers

home help back first fref pref prev next nref lref last post

Re: /mit symlink to attached locker can't be removed

daemon@ATHENA.MIT.EDU (Evan Broder)
Wed Sep 24 23:56:38 2008

Message-ID: <48DB0BC8.2000800@mit.edu>
Date: Wed, 24 Sep 2008 23:55:52 -0400
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: Alex T Prengel <alexp@mit.edu>
CC: Geoffrey Thomas <geofft@mit.edu>, testers@mit.edu
In-Reply-To: <200809192353.m8JNru2Q026955@dit.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hey Alex -
     I think geofft and I are kind of hoping to flip out some weekend 
and fix liblocker and pyhesiodfs and so forth to be internally 
consistent and allow the sort of manipulations that can be traditionally 
done with attach. In the mean time, you can do a bind mount locally over 
the original AFS mountpoint. For example

mount --bind /afs/.athena/software/java_v1.1.6 
/afs/athena/software/java_v.1.1.6

should cause the RW mountpoint to become accessible from 
/mit/java_v1.1.6. This obviously isn't quite ideal, but it makes a good 
temporary solution.

- Evan

Alex T Prengel wrote:
>>> I can attach and add lockers, but detach doesn't remove the /mit symlink,
>>> and root can't delete it:
>>>        
>
>    
>> This is "intentional"; it's a FUSE filesystem. Even if you deleted it, you
>> couldn't create another symlink on top of it, and next time you referenced
>> it at all, it would come back.
>>      
>
>    
>> Are you trying to attach something else (like a read-write locker) on top
>> of it?
>>      
>
> Yes- I absolutely need to have this ability as I maintain many lockers
> that are replicated, and I need to do maintenance in the R/W volumes
> before releasing to the R/O volumes.
>
> i.e. I need to be able to mount /afs/.athena/software/java_v1.1.6 at
> /mit/java_v1.1.6, after /afs/athena/software/java_v1.1.6 had previously
> been mounted there (and vice versa).
>
>    
>> We should probably support this, for locker maintainers. I've
>> reported this as ticket #96 at debathena.mit.edu/trac/.
>>      
>
> Thanks- how do I follow subsequent action on this ticket? I haven't used
> the debathena tracking system before-
>
>                                           Alex
>    

home help back first fref pref prev next nref lref last post