On Wed, 11 Apr 2007, [EMAIL PROTECTED] wrote:
Ultimately, I need to verify what filesystems are actually supported
with fssnap and whether the source filesystem needs to be locked during
the initial startup process for creating the bitmap. From what the man
page apparently states, the source filesystem will need to be write
lockable, and that not all filesystems are supported:
As far as writeable filesystems on Solaris go:
UFS uses/supports the fssnap mechanism.
ZFS has its own snapshot mechanism (it's ingrained in the design
and far more flexible/capable than what fssnap offers)
NFS has no snapshots. Not really applicable - you need to snapshot
the backing filesystem on the NFS server.
PCFS doesn't support snapshotting.
FrankH.
While the snapshot file system is stable and consistent, an
application updating files when the snapshot is created
might leave these files in an internally inconsistent, trun-
cated, or otherwise unusable state. In such a case, the
snapshot will contain these partially written or corrupted
files. It is a good idea to ensure active applications are
suspended or checkpointed and their associated files are
also consistent during snapshot creation.
NOTES
This command might not be supported for all FSTypes.
Thank you again for your time!
This message posted from opensolaris.org
_______________________________________________
ufs-discuss mailing list
[email protected]
_______________________________________________
ufs-discuss mailing list
[email protected]
