On Thu, Oct 04, 2007 at 06:07:24PM +1000, Rick Capaldo wrote:
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.
A shared diskgroup means mounted on both nodes of the cluster at the same time.
There is no failover. For this you need CVM and CFS
As far as how to make diskgroup sharable, you don't have to do anything with
the diskgroup. Just make sure both servers can see the disks in the DG.
-
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.
From the looks of it you'll be
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
James,
As you correctly note in your email, the dmpnodename doesn't affect
functionality. The dmpnodename is really just a 'label' for the DMP
metanode that handles multipathing over the underlying subpaths to a
given LUN.
You have a choice between two namingschemes in SF: Enclosure Based Names
