From: Johan Hartzenberg (jhartzen@csc.com)
Date: Wed Aug 07 2002 - 04:22:08 EDT
Usually when I get an error like "XXXX is not a vxfs file system" it means
I need to fsck the volume. However today it doesn't work, it tells me the
file-system is clean.
Does anybody know what gives?
> zactomut404 [/] # vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c1t8d0s2 sliced - - online
c1t9d0s2 sliced rootmirror rootdg online
c2t2d0s2 sliced - - online
c2t2d18s2 sliced san404d02 san404dg online
c2t6d17s2 sliced san404d01 san404dg online
> zactomut404 [/] # vxprint -g san404dg -v
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0
PUTIL0
v d01 fsgen ENABLED 31457280 - ACTIVE - -
> zactomut404 [/] # mount /D01
vxfs mount: /dev/vx/dsk/san404dg/d01 is not a vxfs file system.
> zactomut404 [/] # fsck -F vxfs /dev/vx/rdsk/san404dg/d01
file system is clean - log replay is not required
> zactomut404 [/] # mount /d01
mount: mount point cannot be determined
> zactomut404 [/] # mount /D01
vxfs mount: /dev/vx/dsk/san404dg/d01 is not a vxfs file system.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:43 EDT