Veritas-bu

[Veritas-bu] Re: file "shrunk by nnnn bytes, padding with zeroes"

2005-08-18 12:31:17
Subject: [Veritas-bu] Re: file "shrunk by nnnn bytes, padding with zeroes"
From: M.W.Ellwood AT rl.ac DOT uk (Ellwood, MW (Mike))
Date: Thu, 18 Aug 2005 17:31:17 +0100
This is a multi-part message in MIME format.

------_=_NextPart_001_01C5A412.41CABF44
Content-Type: text/plain;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Steven,
=20
Yes, actually Marianne recently (re-)pointed us all to the report which
cited Sun bugid  #4502769.
=20
I searched Sunsolve on this, and it came up with 109384-11 (for Sparc),
and I have now installed this patch. Seems ok so far.
=20
Thanks to you both for the useful and timely input.
=20
Regards,
=20
Mike
=20

        -----Original Message-----
        From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Green,
Steven
        Sent: 18 August 2005 17:05
        To: 'veritas-bu AT mailman.eng.auburn DOT edu'
        Subject: [Veritas-bu] Re: file "shrunk by nnnn bytes, padding
with zeroes"
=09
=09

        I ran into this a long time back under 4.5 (currently at
5.1/MP2) on some random Solaris 8 hosts. This issue is a bug in the AIO
driver and a Solaris patch (109384-07 or higher) seemed to address this
issue. According to a Veritas tech I spoke with at the time of the
problem they indicated that the entire file was in fact being backed up
and there was no risk of data loss. The message comes from a timing
anomaly within the AIO driver when the backup process is querying inode
data for the file statistics and getting bogus or garbage data returned.
Apply the latest AIO driver patch and the messages should cease to
appear.

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=20
        #!/usr/steve green :: TDS storage admin :: 608.664.8210 (desk)
:: 608.219.2106 (cell)=20
        It's not that I'm so smart, it's just that I stay with problems
longer.  A. Einstein=20


------_=_NextPart_001_01C5A412.41CABF44
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D494022716-18082005>Hi=20
Steven,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D494022716-18082005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D494022716-18082005>Yes,=20
actually Marianne recently (re-)pointed us all to the report which cited =
Sun=20
bugid&nbsp; #<FONT size=3D2>4502769.</FONT></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D494022716-18082005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D494022716-18082005>I=20
searched Sunsolve on this, and it came up with 109384-11 (for Sparc), =
and I have=20
now installed this patch. Seems ok so far.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D494022716-18082005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D494022716-18082005>Thanks=20
to you both for the useful and timely input.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D494022716-18082005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D494022716-18082005>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D494022716-18082005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D494022716-18082005>Mike</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D494022716-18082005></SPAN></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  veritas-bu-admin AT mailman.eng.auburn DOT edu=20
  [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] <B>On Behalf Of =
</B>Green,=20
  Steven<BR><B>Sent:</B> 18 August 2005 17:05<BR><B>To:</B>=20
  'veritas-bu AT mailman.eng.auburn DOT edu'<BR><B>Subject:</B> [Veritas-bu] =
Re: file=20
  "shrunk by nnnn bytes, padding with zeroes"<BR><BR></FONT></DIV>
  <P><FONT face=3DArial size=3D2>I ran into this a long time back under =
4.5=20
  (currently at 5.1/MP2) on some random Solaris 8 hosts. This issue is a =
bug in=20
  the AIO driver and a Solaris patch (109384-07 or higher) seemed to =
address=20
  this issue. According to a Veritas tech I spoke with at the time of =
the=20
  problem they indicated that the entire file was in fact being backed =
up and=20
  there was no risk of data loss. The message comes from a timing =
anomaly within=20
  the AIO driver when the backup process is querying inode data for the =
file=20
  statistics and getting bogus or garbage data returned. Apply the =
latest AIO=20
  driver patch and the messages should cease to appear.</FONT></P>
  <P><FONT face=3DArial color=3D#0000ff=20
  =
size=3D1>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</F=
ONT>=20
  <BR><FONT face=3DArial color=3D#0000ff size=3D1>#!/usr/steve green :: =
TDS storage=20
  admin :: 608.664.8210 (desk) :: 608.219.2106 (cell)</FONT> <BR><FONT=20
  face=3DArial color=3D#0000ff size=3D1>It's not that I'm so smart, it's =
just that I=20
  stay with problems longer.&nbsp; A. Einstein</FONT>=20
</P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C5A412.41CABF44--

<Prev in Thread] Current Thread [Next in Thread>