[7731] in testers
Re: /mit symlink to attached locker can't be removed
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Fri Sep 19 19:55:14 2008
Message-Id: <200809192353.m8JNru2Q026955@dit.mit.edu>
To: Geoffrey Thomas <geofft@MIT.EDU>
cc: alexp@MIT.EDU, testers@MIT.EDU
In-Reply-To: Your message of "Fri, 19 Sep 2008 19:27:47 EDT."
<alpine.DEB.1.10.0809191919590.32353@vinegar-pot.mit.edu>
Date: Fri, 19 Sep 2008 19:53:56 -0400
From: Alex T Prengel <alexp@MIT.EDU>
>> 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
