Re: [osol-discuss] ZFS root filesystem "/" rollback on a running system!

2009-03-10 Thread Glenn Lagasse
* Stephan Ferraro (cont...@ferraro.net) wrote:
>
> Am 10.03.2009 um 23:02 schrieb Ignacio Marambio Catán:
>
>> you're not supposed to roll back like that, when you upgrade from one
>> build to the next, the process creates a new boot environment (BE) and
>> updates that instead, if you need to go back to how the things were
>> before updating just reboot into the old BE.
>> You can create BEs outside the update process with beadm(1M)
>
>
> I did not an official update. I damaged my root filesystem with a  
> special script.
> However with beadm I can't add a snapshot, because its read-only. I  
> suppose in this case I would need to clone the snapshot into a read- 
> write filesystem and then add it with beadm?

No, you either create a new BE directly via beadm based on your current
BE like so:

beadm create 

This creates a new BE which is identical to what you're currently
running.

Or, you create a new BE based off of an existing BE snapshot thusly:

beadm create ben...@snapshot 

That's all there is to it.

man beadm is your friend :-)

Cheers,

-- 
Glenn
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] ZFS root filesystem "/" rollback on a running system!

2009-03-10 Thread Stephan Ferraro


Am 10.03.2009 um 23:02 schrieb Ignacio Marambio Catán:


you're not supposed to roll back like that, when you upgrade from one
build to the next, the process creates a new boot environment (BE) and
updates that instead, if you need to go back to how the things were
before updating just reboot into the old BE.
You can create BEs outside the update process with beadm(1M)



I did not an official update. I damaged my root filesystem with a  
special script.
However with beadm I can't add a snapshot, because its read-only. I  
suppose in this case I would need to clone the snapshot into a read- 
write filesystem and then add it with beadm?


--
Best regards,
Stephan FERRARO





___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] ZFS root filesystem "/" rollback on a running system!

2009-03-10 Thread stephan.ferraro


Am 10.03.2009 um 23:02 schrieb Ignacio Marambio Catán:


you're not supposed to roll back like that, when you upgrade from one
build to the next, the process creates a new boot environment (BE) and
updates that instead, if you need to go back to how the things were
before updating just reboot into the old BE.
You can create BEs outside the update process with beadm(1M)



I did not an official update. I damaged my root filesystem with a  
special script.
However with beadm I can't add a snapshot, because its read-only. I  
suppose in this case I would need to clone the snapshot into a read- 
write filesystem and then add it with beadm?


--
Best regards,
Stephan FERRARO





___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] ZFS root filesystem "/" rollback on a running system!

2009-03-10 Thread Ignacio Marambio Catán
beadm does all the cloning for you, it even adds an entry to grub

On Tue, Mar 10, 2009 at 8:18 PM, stephan.ferraro
 wrote:
>
> Am 10.03.2009 um 23:02 schrieb Ignacio Marambio Catán:
>
>> you're not supposed to roll back like that, when you upgrade from one
>> build to the next, the process creates a new boot environment (BE) and
>> updates that instead, if you need to go back to how the things were
>> before updating just reboot into the old BE.
>> You can create BEs outside the update process with beadm(1M)
>
>
> I did not an official update. I damaged my root filesystem with a special
> script.
> However with beadm I can't add a snapshot, because its read-only. I suppose
> in this case I would need to clone the snapshot into a read-write filesystem
> and then add it with beadm?
>
> --
> Best regards,
> Stephan FERRARO
>
>
>
>
>
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org


Re: [osol-discuss] ZFS root filesystem "/" rollback on a running system!

2009-03-10 Thread Ignacio Marambio Catán
you're not supposed to roll back like that, when you upgrade from one
build to the next, the process creates a new boot environment (BE) and
updates that instead, if you need to go back to how the things were
before updating just reboot into the old BE.
You can create BEs outside the update process with beadm(1M)

On Tue, Mar 10, 2009 at 7:54 PM, Stephan Ferraro  wrote:
> I just needed to rollback my "/" partition on my running OpenSolaris system 
> snv108.
> I was not sure if it would work because my "/" partition was mounted in 
> read-write.
> When I executed "zfs rollback -r mysnapshot", the system loaded a while and 
> then hanged. I just saw with the virtual console switching an I/O error 
> message.
> I pressed the RESET button on my PC and then I was able to start my old 
> snapshot without any kind of problem!
> I found only a core file of the zfs command in "/". There was written "Bus 
> error".
> I can try to reproduce this if somebody is interessted what is written in the 
> core.
>
> OpenSolaris is a very powerful operating system. I did not know that it was 
> so simple to rollback a running root-filesystem without any kind of dataloss!
> --
> This message posted from opensolaris.org
> ___
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org