A file system cannot be mounted on its corresponding secondary Replication Volume Group VERITAS Volume Replicator volume. Why is this so?

Article:TECH15207  |  Created: 2001-01-04  |  Updated: 2004-01-21  |  Article URL http://www.symantec.com/docs/TECH15207
Article Type
Technical Solution

Environment

Issue



A file system cannot be mounted on its corresponding secondary Replication Volume Group VERITAS Volume Replicator volume. Why is this so?

Error



Error 1:vxfs mount: /dev/vx/dsk/srvmdg/repvol1 is corrupted. needs checking;
Error 2: vxfs mount: read of super-block on /dev/vx/dsk/srvmdg/repvol1 failed: No such device or address.

Error 3: vxfs mount: Cannot open /dev/vx/dsk/srvmdg/repvol1: No such device or address .

Solution



The following describes why errors are returned when attempting to mount a file system on its corresponding secondary Replication Volume Group (RVG) volume:





Sample Configuration







MESSAGE 1


# mount -F vxfs /dev/vx/dsk/srvmdg/repvol1 /repvol1
vxfs mount: /dev/vx/dsk/srvmdg/repvol1 is corrupted. needs checking



MESSAGE 2


# mount -F vxfs /dev/vx/dsk/srvmdg/repvol1 /repvol1
vxfs mount: read of super-block on /dev/vx/dsk/srvmdg/repvol1 failed: No such device or address

or

# mount -F vxfs -o ro /dev/vx/dsk/srvmdg/repvol1 /repvol1
vxfs mount: read of super-block on /dev/vx/dsk/srvmdg/repvol1 failed: No such device or address



MESSAGE 3


# mount -F vxfs -o ro /dev/vx/dsk/srvmdg/repvol1 /repvol1
vxfs mount: Cannot open /dev/vx/dsk/srvmdg/repvol1: No such device or address



Summary of error messages


The error shown in message 1 could show up when the file system is attempted to be started as read-write. The secondary RVG file systems can only be mounted as read-only.

The error shown in message 2 could show up when the RVG is stopped.

The error shown in message 3 could show up when the RVG is stopped and the volume is DISABLED




To test error message 1


Ensure the RVG is ENABLED by typing "vxprint -V <RVG-name>"


# vxprint -V reprvg
Disk group: srvmdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
rv reprvg - DISABLED - - CLEAN - -


If the RVG is not ENABLED, clean as illustrated in the above example and type "vxrvg start <RVG-name>" to start the RVG.


# vxrvg start reprvg



# mount -F vxfs /dev/vx/dsk/srvmdg/repvol1 /repvol1
vxfs mount: /dev/vx/dsk/srvmdg/repvol1 is corrupted. needs checking


However, if trying to mount the file system as read-only, it mounts successfully


# mount -F vxfs -o ro /dev/vx/dsk/srvmdg/repvol1 /repvol1

# df -k /repvol1
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/srvmdg/repvol1 1048576 1630 981512 1% /repvol1





To test error message 2


1. Stop the RVG so it is marked DISABLED. Type "vxprint -V <RVG-name>" to confirm this.


# vxprint -V reprvg
Disk group: srvmdg

TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
rv reprvg - DISABLED - - CLEAN - -



# vxrvg stop reprvg


2. The RVG is now DISABLED and as a result the below errors occur when attempting to mount the file system, either as read-only or read-write


# mount -F vxfs /dev/vx/dsk/srvmdg/repvol1 /repvol1
vxfs mount: read of super-block on /dev/vx/dsk/srvmdg/repvol1 failed: No such device or address


# mount -F vxfs -o ro /dev/vx/dsk/srvmdg/repvol1 /repvol1
vxfs mount: read of super-block on /dev/vx/dsk/srvmdg/repvol1 failed: No such device or address




To test error message 3


1. Stop the RVG by typing the following:

# vxrvg stop reprvg


2. Stop the RVG volume like this:

# vxvol -g srvmdg stop repvol1


3. The error shown below occurs as a result of the above two steps being performed:


# mount -F vxfs -o ro /dev/vx/dsk/srvmdg/repvol1 /repvol1
vxfs mount: Cannot open /dev/vx/dsk/srvmdg/repvol1: No such device or address



Summary


To mount a file system on its corresponding RVG volume, it must meet the following criteria:

- The RVG must be ENABLED
- The RVG volume must be ENABLED
- The file system must be mounted as read-only if on the secondary



Legacy ID



238225


Article URL http://www.symantec.com/docs/TECH15207


Terms of use for this information are found in Legal Notices