Jesus Cea
2008-Nov-08 11:59 UTC
[zfs-discuss] MIgrating to ZFS "root"/"boot" with system in several datasets
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, everybody.
I just trying to upgrade my Solaris 10 Update 6 from UFS to ZFS. But I
want to keep different portions of the OS in different ZFS datasets,
just like I was doing until now. For example, my script to upgrade from
Update 5 to Update 6 was:
"""
[root at tesalia /]# cat z-live_upgrade-Solaris10u6
lucreate -n Solaris10u6 \
-m /:/dev/md/dsk/d0:ufs \
-m /usr/openwin:/dev/md/dsk/d3003:ufs \
-m /usr/dt:/dev/md/dsk/d3004:ufs \
-m /var/sadm:/dev/md/dsk/d3005:ufs \
-m /usr/jdk:/dev/md/dsk/d3006:ufs \
-m /opt/sfw:/dev/md/dsk/d3007:ufs \
-m /opt/staroffice8:/dev/md/dsk/d3008:ufs \
-m /usr/sfw:/dev/md/dsk/d3023:ufs
"""
I would like to be able to place these filesystems in different datasets
under ZFS root/boot, but option "-m" in "lucreate" is not
supported when
upgrading to ZFS.
I would like to have something like:
/pool/ROOT
/pool/ROOT/Sol10u6ZFS
/pool/ROOT/Sol10u6ZFS/usr/openwin <- I want this!
/pool/ROOT/Sol10u6ZFS/usr/dt <- I want this!
...
etc.
Any advice?. Suggestions/alternative approaches welcomed.
- --
Jesus Cea Avion _/_/ _/_/_/ _/_/_/
jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/
jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/_/_/_/
. _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBSRV/KZlgi5GaxT1NAQL+sgP+P6VRu351lkNjF8A18w+BFacLaJxYU7UV
1K9bAHgqdTg/YdlJZHN91Rmq3YEs5vtAzgyoSYxBzhdEO2ZYZl6dvlOO9jCNFFpy
TjK0EBbYPZzl/bJzQVWic4kmEgkKQmdaUM4c4fj2SseEvoI7ZPxdhJn5gT97LiN5
h9NK+cd94UA=qzza
-----END PGP SIGNATURE-----
Ian Collins
2008-Nov-08 20:22 UTC
[zfs-discuss] MIgrating to ZFS "root"/"boot" with system in several datasets
Jesus Cea wrote:> Hi, everybody. > > I just trying to upgrade my Solaris 10 Update 6 from UFS to ZFS. But I > want to keep different portions of the OS in different ZFS datasets, > just like I was doing until now. For example, my script to upgrade from > Update 5 to Update 6 was: > > """ > [root at tesalia /]# cat z-live_upgrade-Solaris10u6 > lucreate -n Solaris10u6 \ > -m /:/dev/md/dsk/d0:ufs \ > -m /usr/openwin:/dev/md/dsk/d3003:ufs \ > -m /usr/dt:/dev/md/dsk/d3004:ufs \ > -m /var/sadm:/dev/md/dsk/d3005:ufs \ > -m /usr/jdk:/dev/md/dsk/d3006:ufs \ > -m /opt/sfw:/dev/md/dsk/d3007:ufs \ > -m /opt/staroffice8:/dev/md/dsk/d3008:ufs \ > -m /usr/sfw:/dev/md/dsk/d3023:ufs > """ > > I would like to be able to place these filesystems in different datasets > under ZFS root/boot, but option "-m" in "lucreate" is not supported when > upgrading to ZFS. > > I would like to have something like: > > /pool/ROOT > /pool/ROOT/Sol10u6ZFS > /pool/ROOT/Sol10u6ZFS/usr/openwin <- I want this! > /pool/ROOT/Sol10u6ZFS/usr/dt <- I want this! > ... > etc. > > Any advice?. Suggestions/alternative approaches welcomed.One obvious question - why? I think it beat to keep everything installed by the OS together in order to maintain a consistent system across upgrades and additional software (like sfw) in another pool, with appropriate mountpoints. You can do the by simply moving the data to the alternative location before migrating. -- Ian.
Jesus Cea
2008-Nov-08 22:24 UTC
[zfs-discuss] MIgrating to ZFS "root"/"boot" with system in several datasets
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1>> Any advice?. Suggestions/alternative approaches welcomed. > One obvious question - why?Two reasons: 1. Backup policies and ZFS properties. 2. I don''t have enough spare space to "rejoin" all system slices in a single one. I thinking in messing with ICF.* files. Seems easy enough to try. - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBSRYRpJlgi5GaxT1NAQI/igP/V/I8yxTPIemBh71Oo6hPcvUYPQVyt8G2 CYkzT+3/3zLPqktHtdEPJzgcqyRyZPhgn14pBuSeMZ6CYZE4Crf3VxAMFwOKBGWX jqCPben0AnJhgbyk+PQvxrPI6vxzzPwPlNWWGv2VZelBdDFbzmdhEUhpF4xW4ACX 7cJX9L3gz6M=uFZh -----END PGP SIGNATURE-----
Lori Alt
2008-Nov-18 21:38 UTC
[zfs-discuss] MIgrating to ZFS "root"/"boot" with system in several datasets
On 11/08/08 15:24, Jesus Cea wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >>> Any advice?. Suggestions/alternative approaches welcomed. >>> >> One obvious question - why? >> > > Two reasons: >The SXCE code base really only supports BEs that are either all in one dataset, or have everything but /var in one dataset and /var in its own dataset (the reason for supporting a separate /var is to be able to set a set a quota on it so growth in log files, etc. can''t fill up a root pool).> 1. Backup policies and ZFS properties. >I can see wanting to do this, but right now, it''s likely to cause problems. Maybe it will be supported eventually.> 2. I don''t have enough spare space to "rejoin" all system slices in a > single one. >Since all parts of Solaris should be in the same pool (whether they are in one dataset or multiple datasets), you need the same amount of space either way. So this is not a valid reason to use multiple datasets.> I thinking in messing with ICF.* files. Seems easy enough to try. > >It might work, but no guarantees. lori> - -- > Jesus Cea Avion _/_/ _/_/_/ _/_/_/ > jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ > jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/_/_/_/ > . _/_/ _/_/ _/_/ _/_/ _/_/ > "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ > "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ > "El amor es poner tu felicidad en la felicidad de otro" - Leibniz > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.8 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iQCVAwUBSRYRpJlgi5GaxT1NAQI/igP/V/I8yxTPIemBh71Oo6hPcvUYPQVyt8G2 > CYkzT+3/3zLPqktHtdEPJzgcqyRyZPhgn14pBuSeMZ6CYZE4Crf3VxAMFwOKBGWX > jqCPben0AnJhgbyk+PQvxrPI6vxzzPwPlNWWGv2VZelBdDFbzmdhEUhpF4xW4ACX > 7cJX9L3gz6M> =uFZh > -----END PGP SIGNATURE----- > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20081118/ba34a434/attachment.html>
Jesus Cea
2008-Nov-25 12:47 UTC
[zfs-discuss] MIgrating to ZFS "root"/"boot" with system in several datasets
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lori Alt wrote:>> The SXCE code base really only supports BEs that are >> either all in one dataset, or have everything but /var in >> one dataset and /var in its own dataset (the reason for >> supporting a separate /var is to be able to set a set a >> quota on it so growth in log files, etc. can''t fill up a >> root pool).OK. I have unified root dataset now. I want to segregate "/var". How is it done by hand?. Must I use a legacy ZFS mountpoint or what?. There is an option for that in "Live Update"?. We are talking about Solaris 10 Update 6. Thanks in advance. - -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/_/_/_/ . _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQCVAwUBSSvzzJlgi5GaxT1NAQIK9gP9GDGDdNvQuB3d2p4lG8TsbnKlKNRLQ1oA jFAGwpD6/0p74fNVFGGZZVsM/6BCxZZlDMUvRygHSOK4TZNV3EuiABOoBCdYtxoV bsCTNwmg4R/fQUUkV8LP+BfQPzTjEaxsn3GpvyYwlS/Fj+lpKOhu4usZlv6cHPqt 73iCnmKDQto=TuCa -----END PGP SIGNATURE-----