Hi Jeff,
Thank you for the clarification on the Copy Date. My investigations
confirm all of this. I'll continue digging on how/way the file timestamps
are not matching up as expected.
Thanks again!
Kris
On Thu, Jan 3, 2019 at 1:47 PM Jeffrey Altman wrote:
> On 1/3/2019 2:54 PM, Kristen Webb
On 1/3/2019 2:54 PM, Kristen Webb wrote:
> This is an old issue that is cropping up in a different way, so I wanted to
> share this before I attempt to perform any sort of repair that might
> lose state.
>
> A client moved a volume and currently the .backup volume copy date does not
> match the
This is an old issue that is cropping up in a different way, so I wanted to
share this before I attempt to perform any sort of repair that might lose
state.
A client moved a volume and currently the .backup volume copy date does not
match the rw volume copy date. As far as I can tell, the
So it turns out that the files servers were backgraded during an OS
upgrade. The client is in
the process of correcting this now. I did find some additional information
from our
logs. The rw volume was unattached and the .backup volume was busy,
indicating a volume
move during our cell scan.
On Fri, Aug 10, 2018 at 02:21:19PM -0600, Kristen Webb wrote:
> I found this situation at a client site and though it was worth brining up:
>
> The client is running openafs 1.8.0-1~ppa0~ubuntu14.04.1-debian, but
> I cannot yet vouch for the server versions.
>
> This is a new volume and here are
I found this situation at a client site and though it was worth brining up:
The client is running openafs 1.8.0-1~ppa0~ubuntu14.04.1-debian, but
I cannot yet vouch for the server versions.
This is a new volume and here are some times from vos exa
CreationThu Aug 9 09:21:40 2018
