Thanks again for the reply!

The data used to reside under /opt/local/crashplan/manifest, after the
reboot there no longer is any data under /opt/local/crashplan/manifest. No
folder, no nothing. The data still does exist, but under
/checkpoints/indestructible/opt/local/crashplan/manifest.

So my questions are 1) why did this happen? 2) how can I properly recover
to my desired state, to have the data r/w under
/opt/local/crashplan/manifest?

BR
Eric


On 24 May 2016 at 16:17, Adam Števko <[email protected]> wrote:

> Hi,
>
> what do you mean by “reappearing"? The data which can be found under
> /checkpoint/indestructible is a snapshot and you can’t move it as they are
> readonly (remember that you can’t mount the snapshot read-write as snapshot
> is read-only copy of filesystem in time).
>
> Cheers,
> Adam
>
>
> On May 24, 2016, at 4:09 PM, Eric Ripa <[email protected]> wrote:
>
> Thanks a lot for the quick reply Adam!
>
> The explanation makes sense, however my aim is not to remove the data,
> rather make the data reappear (mount the latest snapshot rw??) in the
> original location, in this case /opt/local/crashplan
>
> How can I make sure this is done propely? I would rather not lose my ~3 TB
> backup data. :)
>
> Thanks
> Eric
>
>
> On 24 May 2016 at 15:56, Adam Števko <[email protected]> wrote:
>
>> Hi,
>>
>> indestructible_zoneroot is a feature, which shall prevent any accidental
>> deletion of the VM. It is implemented by creaating a snapshot called
>> “indestructible” and is held, which causes any deletetion attempts to fail.
>> /checkpont is a place where all snapshots related to the zone get mounted
>> as lofs. There is a difference in handling of these in SmartOS and in SDC:
>>
>> In SDC, there is a components in system, which automounts these snapshots
>> when they are created.
>> In SmartOS, snapshost is created, but not automatically mounted. When you
>> reboot the zone, the actual list of snapshots is fetched and lofs-mounted
>> into the /checkpoint. If you create snapshot later, it won’t appear under
>> /checkpoint  until you reboot the zone.
>>
>> The readonly filesystem error you saw is caused by the fact, that lofs
>> mount is read-only.
>>
>> If you want to get rid of it either delete zones/<uuid>@indestructible
>> snapshot or run “vmadm update <uuid> indestructible_zoneroot=false” and it
>> should remove the snapshot.
>>
>> Cheers,
>> Adam
>>
>> On May 24, 2016, at 3:44 PM, Eric Ripa <[email protected]> wrote:
>>
>> Hi,
>>
>> I have a LX branded zone running CentOS 6. In it I have a Java-based
>> service called Crashplan.
>>
>> I have the zone protected with
>> "indestructible_zoneroot": true
>>
>> At some point roughly 3-5 days ago all of my backup archives, residing
>> under /opt/local/crashplan, has been *moved* to
>> /checkpoint/indestructible/opt/local/crashplan
>>
>> It is possible that this happened during a vmadm reboot <zoneid>, but I'm
>> not sure.
>>
>>
>> Is this some side-effect of indestructible_zoneroot that I'm unaware off?
>> I tried to 'mv' them back from GZ, but I get this message:
>>
>> mv: cannot unlink
>> /zones/b96a3154-85dc-4a2d-ba80-31affd525667/root/checkpoints/indestructible/opt/local/crashplan/manifest/442330126173077772/cpbf0000000000000129209/442330126173077772:
>> Read-only file system
>>
>> Any pointers of how to proceed? Is it even related to SmartOS at all or
>> is it some CentOS thing?
>>
>> SunOS 0c-c4-7a-69-03-66 5.11 joyent_20160204T173339Z i86pc i386 i86p
>>
>> --
>> Thanks a lot!
>> Eric Ripa
>>
>>
>>
>>
>>
>>
>>
>> http://www.listbox.com
>>
>>
> 
> 


-- 
Hälsningar

*Eric Ripa*
Cloud Engineer

<http://skymill.se/>


Phone
+46 (0) 731 800 502
Email [email protected]
Web skymill.se

[image: twitter] <http://twitter.com/helloskymill>[image: linkedin]
<http://www.linkedin.com/company/skymill-solutions-ab>



-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to