I guess an even better outcome would be for the rename to simply succeed
(either by avoiding whatever the root cause is, or by performing the
"workaround" steps below). I realise I'm preempting the outcome of
whether this works or not, but if I do the following, I get "unmount
failed" too:
opensolaris:~> pfexec beadm create test
opensolaris:~> pfexec beadm activate test
opensolaris:~> beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
snv-111b - - 37.90M static 2009-06-03 09:49
snv-129 - - 189.89M static 2009-12-14 11:57
snv-130 - - 16.68M static 2010-01-04 11:11
snv-131 - - 29.83M static 2010-01-26 11:33
snv-132 N / 186.5K static 2010-02-03 08:40
test R - 22.34G static 2010-02-08 15:58
opensolaris:~> pfexec beadm rename test newtest
Rename of BE test failed.
unmount failed.
Sure enough, truss confirms it received EBUSY from umount2("/").
However, if I re-activate the currently running BE (snv-132), I can then
rename and reactivate the new BE:
opensolaris:~> pfexec beadm activate snv-132
opensolaris:~> pfexec beadm rename test newtest
opensolaris:~> pfexec beadm activate newtest
opensolaris:~> beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
newtest R - 22.34G static 2010-02-08 15:58
snv-111b - - 37.90M static 2009-06-03 09:49
snv-129 - - 189.89M static 2009-12-14 11:57
snv-130 - - 16.68M static 2010-01-04 11:11
snv-131 - - 29.83M static 2010-01-26 11:33
snv-132 N / 4.27M static 2010-02-03 08:40
Is there a technical reason that it cannot rename an activated BE?
Thanks,
Brian
On 02/ 8/10 03:52 PM, Shawn Walker wrote:
On 02/ 8/10 04:32 AM, Brian Ruthven - Solaris Network Sustaining - Sun
UK wrote:
Is the BE that you are trying to rename the currently activated BE (that
is, active on next reboot)?
I ran into problems like this, and had to do a bit of a dance with
"beadm activate" to avoid renaming either the current BE or the
newly-created-and-activated BE:
beadm activate current
beadm rename new latest
beadm activate latest
Admittedly, this was all before the --be-name option came in, so it
could have changed since then. Does the above serve as a useful
workaround?
If that works, then beadm could use some better error messaging for
this case.
--
Brian Ruthven
Solaris Revenue Product Engineering
Sun Microsystems UK
Sparc House, Guillemont Park, Camberley, GU17 9QG
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
