Discussion:
[Veritas-vx] Help ... vx volume is corrupted and doesn't accept fsck command
Rick Capaldo
18 years ago
Permalink
Hi All,

One of my VX volumes is unable to mount. When I try to mount the volume I get:

# mount -F vxfs /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data /mnt
UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data is corrupted. needs checking

If I do a fsck on the volume I get:

# fsck -o full -F vxfs /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data
UX:vxfs fsck: ERROR: V-3-20729: OLT extents conflict
read of primary OLT failed
UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic
read of OLT copy failed
UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue
file system check failure, aborting ...

Is this error terminal or is there a way that I can recover the volume so that it can be mounted?

The state of the volume and plex is ACTIVE ENABLED

v vol-ovpidb-data - ENABLED ACTIVE 134217728 SELECT ovpidb-data-01 fsgen
pl ovpidb-data-01 vol-ovpidb-data ENABLED ACTIVE 134217728 STRIPE 2/128 RW
sd dg-ovpidb01-01 ovpidb-data-01 dg-ovpidb01 0 67108864 0/0 SUN35100_15 ENA
sd dg-ovpidb03-01 ovpidb-data-01 dg-ovpidb03 0 67108864 1/0 SUN35100_17 ENA

Any help would be greatly appreciated.

Thanks,

Rick
A Darren Dunham
18 years ago
Permalink
Post by Rick Capaldo
# mount -F vxfs /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data /mnt
UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data is corrupted. needs checking
This is actually the filesystem that is upset, not the volume (not that
that helps you very much).
Post by Rick Capaldo
# fsck -o full -F vxfs /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data
UX:vxfs fsck: ERROR: V-3-20729: OLT extents conflict
read of primary OLT failed
UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic
read of OLT copy failed
UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue
file system check failure, aborting ...
Is this error terminal or is there a way that I can recover the volume so that it can be mounted?
If 'fsck' isn't helping, then it's well beyond my abilities. I would
open up a support case. They can sometimes work magic.

Do you have any history of why this filesystem might have been
corrupted? Since the volume is okay but the FS is bad, could something
have scribbled over the top of it?
Post by Rick Capaldo
The state of the volume and plex is ACTIVE ENABLED
Right. The volume is probably fine (otherwise you'd get read errors
from fsck).
--
Darren Dunham ***@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
Rick Capaldo
18 years ago
Permalink
Hi All,

In my original email I used the block device for my fsck command instead of the raw device. I would just like to clarify that when I use the raw device I get the same error.

# fsck -o full -F vxfs /dev/vx/rdsk/dg-ovpidb/vol-ovpidb-data
UX:vxfs fsck: ERROR: V-3-20729: OLT extents conflict
read of primary OLT failed
UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic
read of OLT copy failed
UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue
file system check failure, aborting ...

Regards,

Rick

________________________________
From: Rick Capaldo
Sent: Thursday, 4 October 2007 6:07 PM
To: 'veritas-***@mailman.eng.auburn.edu'
Subject: Help ... vx volume is corrupted and doesn't accept fsck command

Hi All,

One of my VX volumes is unable to mount. When I try to mount the volume I get:

# mount -F vxfs /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data /mnt
UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data is corrupted. needs checking

If I do a fsck on the volume I get:

# fsck -o full -F vxfs /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data
UX:vxfs fsck: ERROR: V-3-20729: OLT extents conflict
read of primary OLT failed
UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic
read of OLT copy failed
UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue
file system check failure, aborting ...

Is this error terminal or is there a way that I can recover the volume so that it can be mounted?

The state of the volume and plex is ACTIVE ENABLED

v vol-ovpidb-data - ENABLED ACTIVE 134217728 SELECT ovpidb-data-01 fsgen
pl ovpidb-data-01 vol-ovpidb-data ENABLED ACTIVE 134217728 STRIPE 2/128 RW
sd dg-ovpidb01-01 ovpidb-data-01 dg-ovpidb01 0 67108864 0/0 SUN35100_15 ENA
sd dg-ovpidb03-01 ovpidb-data-01 dg-ovpidb03 0 67108864 1/0 SUN35100_17 ENA

Any help would be greatly appreciated.

Thanks,

Rick
Cornely, David
18 years ago
Permalink
Looks like your Object Location Table is hosed. This table is used to
"locate important file system structural elements."

There is an OLT replica created in case of data corruption but from the
error message below (OLT copy failed) it appears this is also toast.
[mailto:] On Behalf Of Rick Capaldo
55 years ago
Permalink
The VxFS Admin Guide has more details on the OLT and the importance it
plays.



________________________________

From: veritas-vx-***@mailman.eng.auburn.edu
[mailto:veritas-vx-***@mailman.eng.auburn.edu] On Behalf Of Rick
Capaldo
Sent: Thursday, October 04, 2007 14:38
To: 'veritas-***@mailman.eng.auburn.edu'
Subject: Re: [Veritas-vx] Help ... vx volume is corrupted and doesn't
acceptfsck command



Hi All,



In my original email I used the block device for my fsck command instead
of the raw device. I would just like to clarify that when I use the raw
device I get the same error.



# fsck -o full -F vxfs /dev/vx/rdsk/dg-ovpidb/vol-ovpidb-data

UX:vxfs fsck: ERROR: V-3-20729: OLT extents conflict

read of primary OLT failed

UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic

read of OLT copy failed

UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue

file system check failure, aborting ...



Regards,



Rick



________________________________

From: Rick Capaldo
Sent: Thursday, 4 October 2007 6:07 PM
To: 'veritas-***@mailman.eng.auburn.edu'
Subject: Help ... vx volume is corrupted and doesn't accept fsck command



Hi All,



One of my VX volumes is unable to mount. When I try to mount the volume
I get:



# mount -F vxfs /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data /mnt

UX:vxfs mount: ERROR: V-3-21268: /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data
is corrupted. needs checking



If I do a fsck on the volume I get:



# fsck -o full -F vxfs /dev/vx/dsk/dg-ovpidb/vol-ovpidb-data

UX:vxfs fsck: ERROR: V-3-20729: OLT extents conflict

read of primary OLT failed

UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic

read of OLT copy failed

UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue

file system check failure, aborting ...



Is this error terminal or is there a way that I can recover the volume
so that it can be mounted?



The state of the volume and plex is ACTIVE ENABLED



v vol-ovpidb-data - ENABLED ACTIVE 134217728 SELECT
ovpidb-data-01 fsgen

pl ovpidb-data-01 vol-ovpidb-data ENABLED ACTIVE 134217728 STRIPE 2/128
RW

sd dg-ovpidb01-01 ovpidb-data-01 dg-ovpidb01 0 67108864 0/0
SUN35100_15 ENA

sd dg-ovpidb03-01 ovpidb-data-01 dg-ovpidb03 0 67108864 1/0
SUN35100_17 ENA



Any help would be greatly appreciated.



Thanks,



Rick




------_=_NextPart_001_01C806D7.7FE5C5C0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
address
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
font-style:italic;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Arial;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Looks like your Object Location Table is
hosed.&nbsp; This table is used to &#8220;locate important file system structural
elements.&#8221;<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>There is an OLT replica created in case of
data corruption but from the error message below (OLT copy failed) it appears this
is also toast.<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>

Loading...