한번만더 질문드릴게여 mount -p관련.

비정기 조언자

한번만더 질문드릴게여 mount -p관련.

# System /etc/fstab file. Static information about the file systems

# See fstab(4) and sam(1M) for further details on configuring devices.

/dev/vg00/lvol3 / vxfs delaylog 0 1

/dev/vg00/lvol1 /stand vxfs tranflush 0 1

/dev/vg00/lvol4 /home vxfs delaylog 0 2

이것은 vi로fstab을본것이고요

# mount -p

/dev/vg00/lvol3 / vxfs ioerror=nodisable,log,dev=40000003 0 1

/dev/vg00/lvol1 /stand vxfs ioerror=mwdisable,log,nodatainlog,tranflush,dev=40000001 0 0

/dev/vg00/lvol4 /home vxfs ioerror=mwdisable,delaylog,nodatainlog,dev=40000004 0 0

-hosts /net autofs ignore,indirect,nosuid,soft,nobrowse,dev=44000000 0 0

/dev/vg01/lvol1 /data vxfs ioerror=mwdisable,delaylog,nodatainlog,dev=40010001 0 0

이것은 mount -p로본것입니다. -p옵션이 fstab정보를보여주는건데 어건 왜 다르져? 궁금해여~ -초보드림-

1 응답 1

한번만더 질문드릴게여 mount -p관련.

에러가 아닙니다.

즉 VxFS 3.5 버전의 새로 mount 정책이라고 보시면 됩니다.

버젼은 swlist 로 확인하시면 됩니다.

아래의내용을 참조하세요

Since starting on HPUX 11.i and VxFS version 3.5, there is new mount policy

for VxFS 3.5 filesystems. Please refer to the document at:


However, please check /var/adm/syslog/syslog.log for further vxfs messages to

do Filesystem trouble shooting



Sets the policy for handling I/O errors on a mounted file system. I/O errors

can occur while reading or writing file data, or while reading or writing

metadata. The file system can respond to these I/O errors either by halting

or by gradually degrading. The ioerror option provides four policies that

determine how the file system responds to the various errors. All four

policies limit data corruption, either by stopping the file system or by

marking a corrupted inode as bad. The four policies are disable, nodisable,

wdisable, and mwdisable

If wdisable (write disable) or mwdisable (metadata-write disable) is

selected, the file system is disabled or degraded, depending on the type of

error encountered. Select wdisable or mwdisable for environments where read

errors are more likely to persist than write errors, such as when using

non-redundant storage. mwdisable is the default ioerror mount option for

local mounts. See the mount_vxfs(1M) manual page for more information.

Previously (on VxFS 3.1 and 3.3) when filesystem got IO errors, it still

continued to operate, which is bad since in many cases it caused

corruptions, lost user data and recent file updates, etc. The old policy

used by VxFS 3.1 and 3.3 is an analog of "nodisable" in VxFS 3.5.

Since that policy is introduced in version 3.5, then mount -a command will

return with "ioerror=mwdisable" option. This issues exists on both products:

BaseVxFS B.03.50.0 VERITAS File System Bundle for HP-UX

or B3929DA 3.5-ga15-01 HP OnLineJFS 3.5

The BaseVxFS can be downloaded from: