With the release of the Nevada build 90 binaries, it is now possible to install SXCE directly onto a ZFS root filesystem, and also put ZFS swap onto a ZFS filesystem without worrying about having it deadlock. ZFS now also supports crash dumps! To install SXCE to a ZFS root, simply use the text-based installer, after choosing "Solaris Express" from the boot menu on the DVD. DVD download link: http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ This message posted from opensolaris.org
andrew wrote:> With the release of the Nevada build 90 binaries, it is now possible to install SXCE directly onto a ZFS root filesystem, and also put ZFS swap onto a ZFS filesystem without worrying about having it deadlock. ZFS now also supports crash dumps! > > To install SXCE to a ZFS root, simply use the text-based installer, after choosing "Solaris Express" from the boot menu on the DVD. > > DVD download link: > > http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ > >This release also (I beleive) supports installing on ZFS through JumpStart. Does anyone have a pointer for Docs on what the syntax is for a JumpStart profile to configure ZFS root? -Kyle> > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
On Wed, Jun 4, 2008 at 5:01 PM, Kyle McDonald <KMcDonald at egenera.com> wrote:> andrew wrote: > > With the release of the Nevada build 90 binaries, it is now possible to > install SXCE directly onto a ZFS root filesystem, and also put ZFS swap onto > a ZFS filesystem without worrying about having it deadlock. ZFS now also > supports crash dumps! > > > > To install SXCE to a ZFS root, simply use the text-based installer, after > choosing "Solaris Express" from the boot menu on the DVD. > > > > DVD download link: > > > > http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ > > > > > This release also (I beleive) supports installing on ZFS through JumpStart. > > Does anyone have a pointer for Docs on what the syntax is for a > JumpStart profile to configure ZFS root? > > -Kyle > > > > > This message posted from opensolaris.org > > _______________________________________________ > > zfs-discuss mailing list > > zfs-discuss at opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >Does this mean zfs boot/root on sparc is working as well? If so... FINALLY :) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080604/448d8683/attachment.html>
Tim, Start at the zfs boot page, here: http://www.opensolaris.org/os/community/zfs/boot/ Review the information and follow the links to the docs. Cindy ----- Original Message ----- From: Tim <tim at tcsac.net> Date: Wednesday, June 4, 2008 4:29 pm Subject: Re: [zfs-discuss] Get your SXCE on ZFS here! To: Kyle McDonald <KMcDonald at egenera.com> Cc: zfs-discuss at opensolaris.org, andrew <andrum04 at gmail.com>> On Wed, Jun 4, 2008 at 5:01 PM, Kyle McDonald <KMcDonald at egenera.com> > wrote: > > > andrew wrote: > > > With the release of the Nevada build 90 binaries, it is now > possible to > > install SXCE directly onto a ZFS root filesystem, and also put ZFS > swap onto > > a ZFS filesystem without worrying about having it deadlock. ZFS now > also > > supports crash dumps! > > > > > > To install SXCE to a ZFS root, simply use the text-based > installer, after > > choosing "Solaris Express" from the boot menu on the DVD. > > > > > > DVD download link: > > > > > > http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ > > > > > > > > This release also (I beleive) supports installing on ZFS through JumpStart. > > > > Does anyone have a pointer for Docs on what the syntax is for a > > JumpStart profile to configure ZFS root? > > > > -Kyle > > > > > > > > This message posted from opensolaris.org > > > _______________________________________________ > > > zfs-discuss mailing list > > > zfs-discuss at opensolaris.org > > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > > > > > > _______________________________________________ > > zfs-discuss mailing list > > zfs-discuss at opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > > > > Does this mean zfs boot/root on sparc is working as well? If so... FINALLY > :) > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
The FAQ document ( http://opensolaris.org/os/community/zfs/boot/zfsbootFAQ/ ) has a jumpstart profile example: install_type initial_install pool newpool auto auto auto mirror c0t0d0 c0t1d0 bootenv installbe bename sxce_xx The B90 jumpstart "check" program (SPARC) flags that the disks should be specified as: "c0t0d0s0 c0t1d0s0" (slices) Can someone confirm the FAQ is indeed incorrect & perhaps make the adjustment to the FAQ if so warranted? Thanks, -- MikeE -----Original Message----- From: zfs-discuss-bounces at opensolaris.org [mailto:zfs-discuss-bounces at opensolaris.org] On Behalf Of Cindy Swearingen Sent: Wednesday, June 04, 2008 6:50 PM To: Tim Cc: zfs-discuss at opensolaris.org Subject: Re: [zfs-discuss] Get your SXCE on ZFS here! Tim, Start at the zfs boot page, here: http://www.opensolaris.org/os/community/zfs/boot/ Review the information and follow the links to the docs. Cindy ----- Original Message ----- From: Tim <tim at tcsac.net> Date: Wednesday, June 4, 2008 4:29 pm Subject: Re: [zfs-discuss] Get your SXCE on ZFS here! To: Kyle McDonald <KMcDonald at egenera.com> Cc: zfs-discuss at opensolaris.org, andrew <andrum04 at gmail.com>> On Wed, Jun 4, 2008 at 5:01 PM, Kyle McDonald <KMcDonald at egenera.com> > wrote: > > > andrew wrote: > > > With the release of the Nevada build 90 binaries, it is now > possible to > > install SXCE directly onto a ZFS root filesystem, and also put ZFS > swap onto > > a ZFS filesystem without worrying about having it deadlock. ZFS now > also > > supports crash dumps! > > > > > > To install SXCE to a ZFS root, simply use the text-based > installer, after > > choosing "Solaris Express" from the boot menu on the DVD. > > > > > > DVD download link: > > > > > > http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ > > > > > > > > This release also (I beleive) supports installing on ZFS throughJumpStart.> > > > Does anyone have a pointer for Docs on what the syntax is for a > > JumpStart profile to configure ZFS root? > > > > -Kyle > > > > > > > > This message posted from opensolaris.org > > > _______________________________________________ > > > zfs-discuss mailing list > > > zfs-discuss at opensolaris.org > > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > > > > > > _______________________________________________ > > zfs-discuss mailing list > > zfs-discuss at opensolaris.org > > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > > > > Does this mean zfs boot/root on sparc is working as well? If so...FINALLY> :) > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss_______________________________________________ zfs-discuss mailing list zfs-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
On Wed, Jun 04, 2008 at 09:17:05PM -0400, Ellis, Mike wrote:> The FAQ document ( > http://opensolaris.org/os/community/zfs/boot/zfsbootFAQ/ ) has a > jumpstart profile example:Speaking of the FAQ and mentioning the need to use slices, how does that affect the ability of Solaris/ZFS to automatically enable the disk''s cache? Does it need to be manually over-ridden (unlike giving ZFS the whole disk where it automatically turns the disk cache on)? Also, how can you check if the disk''s cache has been enabled or not? Thanks, -brian -- "Coding in C is like sending a 3 year old to do groceries. You gotta tell them exactly what you want or you''ll end up with a cupboard full of pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
format -e is your window to cache settings.
As for the auto-enabling, I''m not sure, as IIRC, we do different things
based on disk technology.
eg: IDE + SATA - Always enabled
SCSI - Disabled by default, unless you give ZFS the whole disk.
I think.
On a couple of my systems, this seems to ring true.
Not at all sure about SAS.
If I''m wrong here, hopefully someone else will provide the complete set
of logic for determining cache enabling semantics.
:)
Nathan.
Brian Hechinger wrote:> On Wed, Jun 04, 2008 at 09:17:05PM -0400, Ellis, Mike wrote:
>> The FAQ document (
>> http://opensolaris.org/os/community/zfs/boot/zfsbootFAQ/ ) has a
>> jumpstart profile example:
>
> Speaking of the FAQ and mentioning the need to use slices, how does that
> affect the ability of Solaris/ZFS to automatically enable the
disk''s
> cache? Does it need to be manually over-ridden (unlike giving ZFS the
> whole disk where it automatically turns the disk cache on)?
>
> Also, how can you check if the disk''s cache has been enabled or
not?
>
> Thanks,
>
> -brian
--
//////////////////////////////////////////////////////////////////
// Nathan Kroenert nathan.kroenert at aus.sun.com //
// Technical Support Engineer Phone: +61 3 9869-6255 //
// Sun Services Fax: +61 3 9869-6288 //
// Level 3, 476 St. Kilda Road //
// Melbourne 3004 Victoria Australia //
//////////////////////////////////////////////////////////////////
On Thu, Jun 05, 2008 at 12:14:46PM +1000, Nathan Kroenert wrote:> format -e is your window to cache settings.Ah ha!> As for the auto-enabling, I''m not sure, as IIRC, we do different things > based on disk technology. > > eg: IDE + SATA - Always enabled > SCSI - Disabled by default, unless you give ZFS the whole disk. > > I think. > > On a couple of my systems, this seems to ring true.Well, I just checked the snv81 box that has ZFS root via Tim''s script, and I know I didn''t enable the cache, so that definitely seems to be true for SATA as the read and write cache of both drives are enabled. Thanks for the pointer to format -e! -brian -- "Coding in C is like sending a 3 year old to do groceries. You gotta tell them exactly what you want or you''ll end up with a cupboard full of pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
Can someone in the know please provide a recipe to upgrade a nv81 (e.g.) to ZFS-root, if possible? That would be, just listing the commands step by step for the uninitiated; for me. Uwe This message posted from opensolaris.org
Cindy.Swearingen at Sun.COM
2008-Jun-05 14:33 UTC
[zfs-discuss] Get your SXCE on ZFS here!
Hi Mike, Sorry for the error. The FAQ example is fixed now. Cindy Ellis, Mike wrote:> The FAQ document ( > http://opensolaris.org/os/community/zfs/boot/zfsbootFAQ/ ) has a > jumpstart profile example: > > install_type initial_install > pool newpool auto auto auto mirror c0t0d0 c0t1d0 > bootenv installbe bename sxce_xx > > The B90 jumpstart "check" program (SPARC) flags that the disks should > be specified as: "c0t0d0s0 c0t1d0s0" (slices) > > Can someone confirm the FAQ is indeed incorrect & perhaps make the > adjustment to the FAQ if so warranted? > > Thanks, > > -- MikeE > > > > -----Original Message----- > From: zfs-discuss-bounces at opensolaris.org > [mailto:zfs-discuss-bounces at opensolaris.org] On Behalf Of Cindy > Swearingen > Sent: Wednesday, June 04, 2008 6:50 PM > To: Tim > Cc: zfs-discuss at opensolaris.org > Subject: Re: [zfs-discuss] Get your SXCE on ZFS here! > > Tim, > > Start at the zfs boot page, here: > > http://www.opensolaris.org/os/community/zfs/boot/ > > Review the information and follow the links to the docs. > > Cindy > > ----- Original Message ----- > From: Tim <tim at tcsac.net> > Date: Wednesday, June 4, 2008 4:29 pm > Subject: Re: [zfs-discuss] Get your SXCE on ZFS here! > To: Kyle McDonald <KMcDonald at egenera.com> > Cc: zfs-discuss at opensolaris.org, andrew <andrum04 at gmail.com> > >>On Wed, Jun 4, 2008 at 5:01 PM, Kyle McDonald <KMcDonald at egenera.com> >>wrote: >> >> >>>andrew wrote: >>> >>>>With the release of the Nevada build 90 binaries, it is now >> >>possible to >> >>>install SXCE directly onto a ZFS root filesystem, and also put ZFS >> >>swap onto >> >>>a ZFS filesystem without worrying about having it deadlock. ZFS now >> >>also >> >>>supports crash dumps! >>> >>>>To install SXCE to a ZFS root, simply use the text-based >> >>installer, after >> >>>choosing "Solaris Express" from the boot menu on the DVD. >>> >>>>DVD download link: >>>> >>>>http://www.opensolaris.org/os/downloads/sol_ex_dvd_1/ >>>> >>>> >>> >>>This release also (I beleive) supports installing on ZFS through > > JumpStart. > >>>Does anyone have a pointer for Docs on what the syntax is for a >>>JumpStart profile to configure ZFS root? >>> >>> -Kyle >>> >>> >>>>This message posted from opensolaris.org >>>>_______________________________________________ >>>>zfs-discuss mailing list >>>>zfs-discuss at opensolaris.org >>>>http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >>>> >>> >>>_______________________________________________ >>>zfs-discuss mailing list >>>zfs-discuss at opensolaris.org >>>http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >>> >> >> >>Does this mean zfs boot/root on sparc is working as well? If so... > > FINALLY > >>:) >>_______________________________________________ >>zfs-discuss mailing list >>zfs-discuss at opensolaris.org >>http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Cindy.Swearingen at Sun.COM
2008-Jun-05 16:09 UTC
[zfs-discuss] Get your SXCE on ZFS here!
Uwe, Please see pages 55-80 of the ZFS Admin Guide, here: http://opensolaris.org/os/community/zfs/docs/ Basically, the process is to upgrade from nv81 to nv90 by using the standard upgrade feature. Then, use lucreate to migrate your UFS root file system to a ZFS file system, like this: 1. Verify you have a current backup. 2. Read the known issues and requirements. 3. Upgrade to nv81 to nv90 using the standard upgrade feature. 4. Migrate your UFS root file system to a ZFS root file system, like this: # zpool create rpool mirror c0t1d0s0 c0t2d0s0 # lucreate -c c0t0d0s0 -n zfsBE -p rpool 5. Activate the ZFS BE, like this: # luactivate zfsBE Please see the doc for more examples of this process. Cindy Uwe Dippel wrote:> Can someone in the know please provide a recipe to upgrade a nv81 (e.g.) to ZFS-root, if possible? > That would be, just listing the commands step by step for the uninitiated; for me. > > Uwe > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Ahhhhhh!!! I can resize swap on a live system. I shudder to think how many times in my sysadmin career I''ve had to resolve insufficient swap issues the HARD WAY with downtime. If I ever meet any ZFS devs your bar tab is covered. This message posted from opensolaris.org
On Thu, 5 Jun 2008, Vincent Fox wrote:> Ahhhhhh!!! > > I can resize swap on a live system. > > I shudder to think how many times in my sysadmin career I''ve had to > resolve insufficient swap issues the HARD WAY with downtime.Umm, you do realise that changing swap size on a live system has been doab for years? "swap -a" is your friend. But yeah, ZFS root rocks! -- Rich Teer, SCSA, SCNA, SCSECA CEO, My Online Home Inventory URLs: http://www.rite-group.com/rich http://www.linkedin.com/in/richteer http://www.myonlinehomeinventory.com
> Umm, you do realise that changing swap size on a live > system has been > doab for years? "swap -a" is your friend.The swap -a not work so great on a single-disk system without a free partition. Many times it was not quite so useful. This is really a nice suprise. This message posted from opensolaris.org
On Fri, Jun 6, 2008 at 7:54 AM, Vincent Fox <vincent_b_fox at yahoo.com> wrote:>> Umm, you do realise that changing swap size on a live >> system has been >> doab for years? "swap -a" is your friend. > > The swap -a not work so great on a single-disk system without a free partition. Many times it was not quite so useful. This is really a nice suprise. >Umm, swapfile ? -- Regards, Cyril
Way to drag my post into the mud there. Ever try adding a swapfile onto the same disk where there''s already a swap partition? At least in my experience this led really poor performance. Can we just move on? This message posted from opensolaris.org
On Thu, Jun 05, 2008 at 10:45:09PM -0700, Vincent Fox wrote:> Way to drag my post into the mud there. > > Can we just move on?Absolutely not! Just be glad you never had to create a swap file on an NFS mount just to be able to build software on your machine! Yes, I really did have to do that. It was 12 years ago, so it was all 10Mbit too. Painful? Yes. Could I at least get my job done? Yes. :-D -brian -- "Coding in C is like sending a 3 year old to do groceries. You gotta tell them exactly what you want or you''ll end up with a cupboard full of pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435)
Cindy.Swearingen at Sun.COM wrote:> Uwe, > > Please see pages 55-80 of the ZFS Admin Guide, here: > > http://opensolaris.org/os/community/zfs/docs/ > > Basically, the process is to upgrade from nv81 to nv90 by using the > standard upgrade feature. Then, use lucreate to migrate your UFS root > file system to a ZFS file system, like this: > > 1. Verify you have a current backup. > 2. Read the known issues and requirements. > 3. Upgrade to nv81 to nv90 using the standard upgrade feature. > 4. Migrate your UFS root file system to a ZFS root file system, > like this: > # zpool create rpool mirror c0t1d0s0 c0t2d0s0 > # lucreate -c c0t0d0s0 -n zfsBE -p rpool > 5. Activate the ZFS BE, like this: > # luactivate zfsBE > > Please see the doc for more examples of this process. > > Cindy >Hi Cindy, unfortunately, this approach fails for me, because lucreate errors out (see below). Does anybody know, if this is a known issue? - Thomas # lucreate -n nv90ext -p ext1 Analyzing system configuration. Comparing source boot environment <c0t1d0s0> file systems with the file system(s) you specified for the new boot environment. Determining which file systems should be in the new boot environment. Updating boot environment description database on all BEs. Updating system configuration files. The device </dev/dsk/c1t9d0> is not a root device for any boot environment; cannot get BE ID. Creating configuration for boot environment <nv90ext>. Source boot environment is <c0t1d0s0>. Creating boot environment <nv90ext>. Creating file systems on boot environment <nv90ext>. Creating <zfs> file system for </> in zone <global> on <ext1/ROOT/nv90ext>. Populating file systems on boot environment <nv90ext>. Checking selection integrity. Integrity check OK. Populating contents of mount point </>. Copying. WARNING: The file </tmp/lucopy.errors.5981> contains a list of <45> potential problems (issues) that were encountered while populating boot environment <nv90ext>. INFORMATION: You must review the issues listed in </tmp/lucopy.errors.5981> and determine if any must be resolved. In general, you can ignore warnings about files that were skipped because they did not exist or could not be opened. You cannot ignore errors such as directories or files that could not be created, or file systems running out of disk space. You must manually resolve any such problems before you activate boot environment <nv90ext>. Creating shared file system mount points. Creating compare databases for boot environment <nv90ext>. Creating compare database for file system </>. Updating compare databases on boot environment <nv90ext>. Making boot environment <nv90ext> bootable. ERROR: Unable to determine the configuration of the target boot environment <nv90ext>. ERROR: Update of loader failed. ERROR: Cannot make ABE <nv90ext> bootable. Making the ABE <nv90ext> bootable FAILED. ERROR: Unable to make boot environment <nv90ext> bootable. ERROR: Unable to populate file systems on boot environment <nv90ext>. ERROR: Cannot make file systems for boot environment <nv90ext>. $ cat /tmp/lucopy.errors.5981 Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/template" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/latest" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/1/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/4/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/5/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/14/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/16/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/18/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/19/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/23/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/25/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/28/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/37/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/43/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/44/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/45/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/46/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/47/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/48/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/51/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/52/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/53/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/55/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/56/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/57/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/58/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/59/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/60/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/62/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/63/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/64/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/68/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/78/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/79/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/83/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/85/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/93/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/94/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/95/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/96/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/97/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/98/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/process/99/ctl" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/device/template" Restoring existing "/.alt.tmp.b-aEb.mnt/system/contract/device/latest"