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 <jalt...@auristor.com> wrote: > 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 rw volume copy date. As far as I can tell, the version of > > openafs was > > 1.8.2 (I am confirming this now). > > > > Here are some current time stamps: > > > > # vos ex test.volume > > Copy Thu Nov 29 15:10:47 2018 > > > > # vos ex test.volume.backup > > Copy Fri Nov 30 02:38:44 2018 > > > > When I try to manually update the .backup volume the Copy time > > is unchanged and still different from the rw volume. > > > > Kris, > > I'm not sure what if any data corruption is taking place during volume > moves with OpenAFS 1.8.x but I believe looking at the volume Copy date > is a red herring. OpenAFS destroys the ".backup" as part of a RW volume > move. Therefore, the "Copy" date is not expected to match the "Copy" > date of the RW when the BACK is re-created. > > The Copy field displays the date and time this copy of this volume was > created. This is the time when the volume was created on the File Server > and partition from which statistics are obtained. > > For read/write volumes, it is the date and time of initial creation if > the volume has never been moved or restored, or the date and time of the > most recent move or restore operation. > > For read-only volumes, it is the date and time of the initial vos > release command that copied the volume data to the File Server and > partition. > > For backup volumes, it is the date and time of the initial vos backup or > vos backupsys command on the specified File Server and partition. It > will match the Creation field. > > The copy date is not stored in volume dumps and cannot be restored or > migrated to another File Server or partition. > > Jeffrey Altman > > -- This message is NOT encrypted -------------------------------- Mr. Kristen J. Webb Chief Technology Officer Teradactyl LLC. 2450 Baylor Dr. S.E. Albuquerque, New Mexico 87106 Phone: 1-505-338-6000 Email: kw...@teradactyl.com Web: http://www.teradactyl.com Providers of Scalable Backup Solutions for Unique Data Environments -------------------------------- NOTICE TO RECIPIENTS: Any information contained in or attached to this message is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this transmittal, you are hereby notified that you received this transmittal in error, and we request that you please delete and destroy all copies and attachments in your possession, notify the sender that you have received this communication in error, and note that any review or dissemination of, or the taking of any action in reliance on, this communication is expressly prohibited. Regular internet e-mail transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate, and it should not be relied upon as such. If you prefer to communicate with Teradactyl LLC. using secure (i.e., encrypted and/or digitally signed) e-mail transmission, please notify the sender. Otherwise, you will be deemed to have consented to communicate with Teradactyl via regular internet e-mail transmission. Please note that Teradactyl reserves the right to intercept, monitor, and retain all e-mail messages (including secure e-mail messages) sent to or from its systems as permitted by applicable law
