How to use _netdev options for mounting the filesystems in Novell Suse 11

book

Article ID: 100005470

calendar_today

Updated On:

Description

Error Message

UX-vxfs fsk.vxfs: ERROR: v-3-20276: cannot stat /dev/vx/dsk/testdg/testvol   while systems boots

Cause

/# NOTE: When adding or modifying VxFS or VxVM entries, add '_netdev'
# to the mount options to ensure the filesystems are mounted after VxVM and
# VxFS have started.

/dev/vx/dsk/testdg/testvol      /test   vxfs    convosync=direct,_netdev        0  1 

With this configuration, system  will run the fsck during the  boot and it fails with error message
 UX-vxfs fsk.vxfs: ERROR: v-3-20276: cannot stat /dev/vx/dsk/testdg/testvol   while systems boots

 

 
 

 

 

Resolution

The mount command automatically runs the VxFS fsck command to clean up the intent log if the mount command detects a dirty log in the file system.

This functionality is only supported on file systems mounted on a Veritas Volume Manager (VxVM) volume.

Editing the fstab file : You can edit the /etc/fstab file to mount a file system automatically at boot time.

You must specify the following:
- The special block device name to mount
- The mount point
- The file system type (vxfs)
- The mount options, which must include the -O _netdev option
- Which file systems need to be dumped (by default a file system is not dumped)
- Which fsck pass looks at the file system 

Solution:  Please add the following entries to /etc/fstab and reboot the server.

vi /etc/fstab

/dev/vx/dsk/testdg/testvol      /test   vxfs    convosync=direct,_netdev        0  0

We will ensure that file systems get fscked after the reboot. The rc scripts which call vxvm-boot will run fsck on all volumes with _netdev option after reboot.

# grep -R -i fsck rc*
rc2.d/S01vxvm-boot:     fsck -A -T -R -a -t opts=_netdev
rc2.d/K02vxvm-boot:     fsck -A -T -R -a -t opts=_netdev

 

 

 

Issue/Introduction

How to use _netdev options for mounting the filesystems in Linux Env.