Also, that thread mentions that you may use this work around with the read-only dataset with the pool to enable writes to the dataset and keeping it read-only before exporting the pool. Still, yes, "budy" mentions setting the dataset attribute while the pool is imported read-only (Stephan? would you chime in with more details, if that's really you?)
If you manage to reproduce this trick in command-line and if it does indeed help (and if you want to keep using this pool i.e. to help the developers reproduce and fix the core problem) instead of just remaking the pool, you might build on the (unbaked as of yet) scripts and SMF manifests here: http://wiki.openindiana.org/oi/Advanced+-+ZFS+Pools+as+SMF+services+and+iSCSI+loopback+mounts This would enable you to code all this logic about setting and removing the readonly bits from your pool around the import-as-a-service, so that your system would "gracefully" import the pool, enable the dataset, etc. and undo this upon proper shutdown. HTH, //Jim Klimov _______________________________________________ OpenIndiana-discuss mailing list [email protected] http://openindiana.org/mailman/listinfo/openindiana-discuss
