On 2014-04-01, at 01:31, Andrew Deason wrote:
<---cut--->
> The NAT64 scheme I
> think was brought up in case we could work in that environment with
> minimal changes to OpenAFS, but as far as I can tell the answer to that
> is just "no".
>
> It sounded like you were satisfied with the answers I
During the end of the (running-behind-schedule) IPv6 talk at this year's
EAKC, I believe it was George Sluyterman that asked about the
possibility of using NAT64 with OpenAFS. While on stage, Simon and I
didn't really answer this question (I was a little confused, and wasn't
sure if I was hearing '
On Tue, Mar 11, 2014 at 11:33:37AM -0500, Andrew Deason wrote:
> [Moving from openafs-info to openafs-devel.]
>
> On Tue, 11 Mar 2014 11:45:47 -0400
> "J. Bruce Fields" wrote:
>
> > - d_materialise_unique: which was originally designed which
> > distributed filesystems in mind, which h
Can an openafs developer (who is knowledgeable about the details of this issue)
open a redhat bugzilla case on this (if not already done).
SLAC's redhat TAM said this will be the best way to get traction on this. He
wants to link all the Red Hat customer cases to a bugzilla case.
SLAC's redhat T
> I've opened Case #01053566 with Red Hat today for USGS.
>
> - Ken
SLAC has Red Hat case # 01051669 opened on this.
I have made a request in our case to link to your case to add weight to the
issue.
Karl
:�� T���&j)b� b�өzpJ)ߢ�^��좸!��l��b��(���~�+Y���b�ا~�~ȧ~
Update - Oracle has implemented a similar optimization as Linux has, so now
VFS layer will check if an object already exists and if it does it won't
even call a fs-specific callback. AFS and NFS benefit most. This is in
Solaris 11 + SRU17, and will be part of 11.2 release as well.
> -Origin
