fsck issues


		< Previous \| TOC \| Index \| Next >

fsck issues

Running fsck before upgrading to 5.0

Before upgrading to SFCFS 5.0, make sure that all the file systems are clean by running the fsck command. See the fsck(1M) manual page.

The fsck command replays the intent log to complete any outstanding transactions, then marks the file system as clean.

Warning: You must run fsck before upgrading an existing cluster file system to 5.0. If you upgrade to 5.0, and then run the fsck command, it will fail due to the incompatibility of older fsck binaries with the new kernel.

See the Veritas Storage Foundation Cluster File System Installation Guide for additional information on upgrade issues.

fsck may abort when applied to unclean file systems from VxFS 4.0

Due to an incompatibility in the VxFS fsck utility between the 5.0 and 4.0 releases, fsck may abort during intent log replay if it is run on older file systems. This only affects file systems that:

were previously running under VxFS 4.0
were multi-volume file systems or file systems on shared volumes
have not been cleanly unmounted prior for use in 5.0


^ Return to Top	< Previous \| TOC \| Index \| Next >