[OpenAFS] possible microsoft excel 2010 corruption issue on openafs
volumes
info@probanet.it
info@probanet.it
Wed, 14 Dec 2011 15:27:14 +0100
On Wed, 14 Dec 2011 08:47:46 -0500, Derrick Brashear <shadow@gmail.com>=0D
wrote:=0D
> /afs/andrew.cmu.edu/usr/shadow/patch1=0D
> fixes the issue=0D
> /afs/andrew.cmu.edu/usr/shadow/patch2=0D
> fixes some warnings due to unused variables that the first patch didn't=
=0D
> remove=0D
> =0D
> A 1.6.1 release candidate containing these should be available within=0D
> the next 24 hours.=0D
=0D
Thank you very much! ^_^ So I think we'll wait for the RC and then compil=
e=0D
it! Thanks again!!=0D
=0D
Stefano=0D
Fabio=0D
=0D
=0D
> On Wed, Dec 14, 2011 at 4:36 AM, <info@probanet.it> wrote:=0D
>> Hello!=0D
>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 We're experiencing the same=
issue on a large number of volumes=0D
>> (around=0D
>> 28000, just finished upgrading fileserver to 1.6.0 in order to use=0D
DAFS,=0D
>> using Ubuntu 11.10 x86_64). Our volumes doesn't have a .backup, just R=
W=0D
>> + RO (1 cheap-replica and 1 remote replica). Where can we find a patch=
=0D
>> and how should we use it? Thanks for your help! :)=0D
>>=0D
>> Stefano=0D
>> Fabio=0D
>>=0D
>>=0D
>>=0D
>> On Wed, 7 Dec 2011 19:23:50 -0500, Derrick Brashear <shadow@gmail.com>=
=0D
>> wrote:=0D
>>=0D
>> there's an issue in the 1.6.0 fileserver but if you are also having it=
=0D
on=0D
>> 1.4.14 that's new=0D
>>=0D
>> Derrick=0D
>>=0D
>> On Dec 7, 2011, at 19:19, Jonathan Nilsson <jnilsson@uci.edu> wrote:=0D
>>=0D
>> Hello,=0D
>> We've had some strange file corruption and missing data issues with=0D
>> Microsoft Excel 2010 on a Windows 7 OpenAFS 1.5.78 client.=0D
>> 1) A user creates an Excel file on their local drive, then copies it t=
o=0D
>> an=0D
>> AFS RW mount point (via mapped network drive).=0D
>> 2) several clients read the file (no changes made)=0D
>> 3) at some point the file is no longer able to be opened, or it opens=0D
but=0D
>> warns of corruption and missing data=0D
>> When I recover the file from the backup on the day of the file's=0D
>> modification timestamp, the restored file is fine. Curiously, the=0D
>> restored=0D
>> file appears identical to the corrupted file: the file size (bytes) an=
d=0D
>> timestamp are identical.=0D
>> The fileservers housing volumes where this has happened are:=0D
>> =C2=A0CentOS 6.0 2.6.32-71.29.1.el6.x86_64 with OpenAFS 1.6.0=0D
>> =C2=A0RHEL 6.1 2.6.32-131.2.1.el6.x86_64 with OpenAFS 1.4.14=0D
>> We have upgraded the client to OpenAFS 1.7.2 (we did this just before=0D
the=0D
>> 1.7.3 announcement) hoping to fix the issue if it is a bug...=C2=A0Is =
there=0D
>> any=0D
>> known issue with 1.5.78 client that could have caused corruption like=0D
>> this?=0D
>> --=0D
>> Jonathan.Nilsson at uci dot edu=0D
>> Social Sciences Computing Services=0D
>> SSPB 1265 | 949.824.1536=0D
>>=0D
>>