On Mar 20, 2008, at 3:59 PM, Robert Milkowski wrote: > Hello Cyril, > > Thursday, March 20, 2008, 9:51:35 PM, you wrote: > > CP> On Thu, Mar 20, 2008 at 11:26 PM, Mark A. Carlson > <[EMAIL PROTECTED]> wrote: >>> >>> I think the answer is that the configuration is hidden >>> and cannot be backed up so that it can be easily restored >>> to a brand spanking new machine with new disks. > > CP> Hm, to which I can add that "zpool history" will keep forever the > CP> zpool command that created the pool initially. And it can be > easily > CP> copy/pasted somewhere else in order to be used as is or as a > template > CP> for a similar configuration. > > > Will it? I thought zpool history is a cyclic buffer...
It is - except for the initial creation of the pool: http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/ common/fs/zfs/spa_history.c#52 http://blogs.sun.com/erickustarz/entry/zpool_history So even with the above, if you add a vdev, slog, or l2arc later on, that can be lost via the history being a ring buffer. There's a RFE for essentially taking your current 'zpool status' output and outputting a config (one that could be used to create a brand new pool): 6276640 zpool config > Then pool configuration is not only raid configuration - it's also all > datasets and their properties like share parameters, etc. Very true. eric _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
