Cannot find directory inode 0

Question

Friend,
In Solaris 10 we took dump of a vxfs file system at run level 3 using vxdump to LTO4 tape but while restoring it back using vxrestore command we are getting an error as "cannot find directory inode 0 abort[yn]"
-> ossdg/export (2011-08-09 16:46:52)
Using 'vxdump' to store
vxfs vxdump: Date of this level 0 dump: Tue Aug 09 16:46:52 2011
vxfs vxdump: Date of last level 0 dump: the epoch
Dumping /dev/vx/rdsk/ossdg/export_m2 to /dev/rmt/0un
vxfs vxdump: mapping (Pass I) [regular files]
vxfs vxdump: mapping (Pass II) [directories]
vxfs vxdump: estimated 11178068 blocks (5458.04MB) on 0.01 tape(s).
vxfs vxdump: dumping (Pass III) [directories]
vxfs vxdump: dumping (Pass IV) [regular files]
vxfs vxdump: vxdump: 5596521 tape blocks on 1 volumes(s)
vxfs vxdump: Closing /dev/rmt/0un
vxfs vxdump: vxdump is done
-> ossdg/export (2011-08-09 16:46:52)
Using 'vxdump' to store
vxfs vxdump: Date of this level 0 dump: Tue Aug 09 16:46:52 2011
vxfs vxdump: Date of last level 0 dump: the epoch
Dumping /dev/vx/rdsk/ossdg/export_m2 to /dev/rmt/0un
vxfs vxdump: mapping (Pass I) [regular files]
vxfs vxdump: mapping (Pass II) [directories]
vxfs vxdump: estimated 11178068 blocks (5458.04MB) on 0.01 tape(s).
vxfs vxdump: dumping (Pass III) [directories]
vxfs vxdump: dumping (Pass IV) [regular files]
vxfs vxdump: vxdump: 5596521 tape blocks on 1 volumes(s)
vxfs vxdump: Closing /dev/rmt/0un
vxfs vxdump: vxdump is done
-> ossdg/export (2011-08-09 16:46:52)
Using 'vxdump' to store
vxfs vxdump: Date of this level 0 dump: Tue Aug 09 16:46:52 2011
vxfs vxdump: Date of last level 0 dump: the epoch
Dumping /dev/vx/rdsk/ossdg/export_m2 to /dev/rmt/0un
vxfs vxdump: mapping (Pass I) [regular files]
vxfs vxdump: mapping (Pass II) [directories]
vxfs vxdump: estimated 11178068 blocks (5458.04MB) on 0.01 tape(s).
vxfs vxdump: dumping (Pass III) [directories]
vxfs vxdump: dumping (Pass IV) [regular files]
vxfs vxdump: vxdump: 5596521 tape blocks on 1 volumes(s)
vxfs vxdump: Closing /dev/rmt/0un
vxfs vxdump: vxdump is done
-> Restore ossdg/export 2011-08-17 18:42:18
Positioning tape at block 10
New vxfs FS on export
vxrestore -c export
UX:vxfs vxrestore: ERROR: V-3-24789: expected next file 1408, got 1405
UX:vxfs vxrestore: ERROR: V-3-24789: expected next file 16547, got 16546
cannot find directory inode 0
abort [yn] abort [yn]
What will be the possible reason of this error? Can be ignore this error and continue further?
Thanks,
Srikanta Sanpui

Answer 1

Srikantada,
Found some instances of similar problems. Hope you"ll find these useful.
(From http://sfdoccentral.symantec.com/sf/4.1/solaris/manpages/vxfs/vxrestore_1m.html)
{quote}*expected next file +inumber+ got +inumber+*
A file not listed in the directory appeared. This can occur when using a dump tape created on an active file system. Dumps should be performed with the file system unmounted or with the system in single-user mode (see the init(1M) manual page) to ensure a consistent dump. The dump can also be performed in the multi-user environment using a snapshot file system with the online backup facility (see the snapof= filesystem option of the VxFS mount command{quote}
Another conversation suggests that the /etc/vfstab file might be messed up.
(From http://www.sunmanagers.org/pipermail/summaries/2004-June/005246.html)
{quote}Check your /etc/vfstab file very carefully: I suspect you may find that
the line for / looks something like
/dev/dsk/c0t8d0s0 /dev/rdsk/c0t0d0s0 / ufs #[...]
instead of
/dev/dsk/c0t8d0s0 /dev/rdsk/c0t8d0s0 / ufs #[...]
When certain filesystem tools are given a block device (/dev/dsk/*),
they consult /etc/vfstab to find out the name of the corresponding raw
device (/dev/rdsk/*).
If this is in fact your problem, then note that ufsdump uses a similar
algorithm: any backups you've made could be of the wrong device.{quote}
Good luck :)