[EMAIL PROTECTED] said: > # ludelete beA > ERROR: cannot open 'pool00/zones/global/home': dataset does not exist > ERROR: cannot mount mount point </.alt.tmp.b-QY.mnt/home> device > <pool00/zones/global/home> > ERROR: failed to mount file system <pool00/zones/global/home> on > </.alt.tmp.b-QY.mnt/home> > ERROR: unmounting partially mounted boot environment file systems > ERROR: cannot mount boot environment by icf file </etc/lu/ICF.1> > ERROR: Cannot mount BE <beA>. > Unable to delete boot environment. > . . . > Big Mistake... For ZFS boot I need space for a seperate zfs root pool. So > whilst booted under beB I backup my pool00 data, destroy pool00, re-create > pool00 (a little differently, thus the error it would seem) but hold out one > of the drives and use it to create a rpool00 root pool. Then I > . . .
I made this same mistake. If you "grep pool00 /etc/lu/ICF.1" you'll see filesystems beA expects to be mounted in beA; Some of those it may expect to be able to share between the current BE and beA. The way to fix things is to create a temporary pool "pool00"; This need not be on an actual disk, it could be hosted in a file or a slice, etc. Then create those datasets in the temporary pool, and try the "ludelete beA" again. Note that if the problem datasets are supposed to be shared between current BE and beA, you'll need them mounted on the original paths in the current BE, because "ludelete" will use loopback mounts to attach them into beA during the deletion process. I guess the moral of the story is that you should ludelete any old BE's before you alter the filesystems/datasets that it mounts. Regards, Marion _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
