hi all, I am new to solaris. I am creating a zfs filestore which should boot via rootfs. The version of the system is: SunOS store1 5.10 Generic_118855-33 i86pc i386 i86pc. Now I have seen that there is a new rootfs support for solaris starting with build: snv_62. (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) Is it a) possible to start from a raidz pool? b) possible to update my version using a patch from the web to the above version? thanks in advance -- Jakob
On 4/5/07, Jakob Praher <jp at hapra.at> wrote:> hi all,Hi Jacob,> > I am new to solaris. > I am creating a zfs filestore which should boot via rootfs. > The version of the system is: SunOS store1 5.10 Generic_118855-33 i86pc > i386 i86pc. > > Now I have seen that there is a new rootfs support for solaris starting > with build: snv_62. > (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) > > Is it > a) possible to start from a raidz pool?No. At this point raidz pool is not usable as a boot pool.> b) possible to update my version using a patch from the web to the above > version?Generally speaking there is no patch to get your system from any 5.x release to 5.x+1 release. You may, however, upgrade your current system from SunOS 5.10 to Nevada using regular LiveUpgrade or DeadUpgrade(TM) procedure. (I would just install from scratch - assuming you have all your valuable data stored externally or on exportable zpool) -- Regards, Cyril
Hi Cyril, thanks for your quick response! Cyril Plisko wrote:> On 4/5/07, Jakob Praher <jp at hapra.at> wrote: >> hi all, > >> >> I am new to solaris. >> I am creating a zfs filestore which should boot via rootfs. >> The version of the system is: SunOS store1 5.10 Generic_118855-33 i86pc >> i386 i86pc. >> >> Now I have seen that there is a new rootfs support for solaris starting >> with build: snv_62. >> (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) >> >> Is it >> a) possible to start from a raidz pool? > > No. At this point raidz pool is not usable as a boot pool. >Is this possible then to use a mirror pool?>> b) possible to update my version using a patch from the web to the above >> version? > > Generally speaking there is no patch to get your system from any 5.x > release > to 5.x+1 release. You may, however, upgrade your current system from > SunOS 5.10 to Nevada using regular LiveUpgrade or DeadUpgrade(TM) > procedure. > > (I would just install from scratch - assuming you have all your valuable > data stored externally or on exportable zpool) >So to get this right: Nevada == Solaris Express?! This is a little bit confusing. I am very glad Ian Murdock joined Sun. Hopefully system upgrade will be as easy as apt-get dist-upgrade. Is there any easy way to just get the latest solaris kernel via web? thanks Jakob
> >> a) possible to start from a raidz pool? > > > > No. At this point raidz pool is not usable as a boot pool. > > Is this possible then to use a mirror pool?Yes (to some extent). You can use one disk/slice or a mirror. 2. Prepare the disk for a ZFS rootpool. A rootpool can be a single disk device, or a device slice, or in a mirrored configuration. If you use a whole disk for a rootpool, you must use a slice notation (e.g. c0d0s0) so that it is labeled with an SMI label. I don''t think you can use multiple mirrors (striped mirrors).> > Generally speaking there is no patch to get your system from any 5.x > > release > > to 5.x+1 release. You may, however, upgrade your current system from > > SunOS 5.10 to Nevada using regular LiveUpgrade or DeadUpgrade(TM) > > procedure. > > > > (I would just install from scratch - assuming you have all your valuable > > data stored externally or on exportable zpool) > > > So to get this right: > Nevada == Solaris Express?!Sort of. Nevada is the development code name for the next version of Solaris, currently under development. Solaris Express is a bootable, runnable snapshot of that development. Sometimes features that go into Nevada are backported to already released versions of Solaris (like ZFS was). It is possible that the rootpool stuff will be someday. But I doubt that would happen before the installer work to support rootpool is complete.> This is a little bit confusing. > I am very glad Ian Murdock joined Sun. Hopefully system upgrade will be > as easy as apt-get dist-upgrade. > Is there any easy way to just get the latest solaris kernel via web?The source is always available, but you can''t necessarily just compile a new kernel and plop it into place and expect it to work. If you want an installable version of Solaris Express, go here: http://www.opensolaris.org/os/downloads/ You can get a CD or DVD version. Note that the installable ISOs lag a bit from the source. Right now when I look, the ISOs are at build 61. You''d need to wait for build 62 for the rootfs support mentioned. -- Darren Dunham ddunham at taos.com Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. >
But even with b62, you won''t be able to start with the zfs mirror right? You''ll have to do UFS then convert it? Malachi On 4/5/07, Darren Dunham <ddunham at taos.com> wrote:> > > >> a) possible to start from a raidz pool? > > > > > > No. At this point raidz pool is not usable as a boot pool. > > > > Is this possible then to use a mirror pool? > > Yes (to some extent). You can use one disk/slice or a mirror. > > 2. Prepare the disk for a ZFS rootpool. A rootpool can be a single > disk device, or a device slice, or in a mirrored configuration. If > you use a whole disk for a rootpool, you must use a slice notation > (e.g. c0d0s0) so that it is labeled with an SMI label. > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070405/a8bc9aa5/attachment.html>
On Thu, 2007-04-05 at 14:27 -0700, Malachi de ?lfweald wrote:> But even with b62, you won''t be able to start with the zfs mirror > right? You''ll have to do UFS then convert it? > > MalachiCorrect. The direct support for installing on ZFS as root will come with the fixing of the Install binary, which (I''m told) is a bit away (I take it to mean about 10 builds or so - figure a couple of months). -- Erik Trimble Java System Support Mailstop: usca14-102 Phone: x17195 Santa Clara, CA Timezone: US/Pacific (GMT-0800)
On 05/04/07, Jakob Praher <jp at hapra.at> wrote:> Hi Cyril, > > thanks for your quick response! > Cyril Plisko wrote: > > On 4/5/07, Jakob Praher <jp at hapra.at> wrote: > >> hi all, > > > >> > >> I am new to solaris. > >> I am creating a zfs filestore which should boot via rootfs. > >> The version of the system is: SunOS store1 5.10 Generic_118855-33 i86pc > >> i386 i86pc. > >> > >> Now I have seen that there is a new rootfs support for solaris starting > >> with build: snv_62. > >> (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) > >> > >> Is it > >> a) possible to start from a raidz pool? > > > > No. At this point raidz pool is not usable as a boot pool. > > > > Is this possible then to use a mirror pool? > > >> b) possible to update my version using a patch from the web to the above > >> version? > > > > Generally speaking there is no patch to get your system from any 5.x > > release > > to 5.x+1 release. You may, however, upgrade your current system from > > SunOS 5.10 to Nevada using regular LiveUpgrade or DeadUpgrade(TM) > > procedure. > > > > (I would just install from scratch - assuming you have all your valuable > > data stored externally or on exportable zpool) > > > So to get this right: > Nevada == Solaris Express?! > > This is a little bit confusing. > I am very glad Ian Murdock joined Sun. Hopefully system upgrade will be > as easy as apt-get dist-upgrade. > Is there any easy way to just get the latest solaris kernel via web?Know that efforts were in place a long time ago to streamline the upgrade and update processes. Ian did not join Sun (as far as I know) to make any change to Solaris directly or its processes. Any success in this area should be attributed to the teams already working on solutions, thanks :) -- "Less is only more where more is no good." --Frank Lloyd Wright Shawn Walker, Software and Systems Analyst binarycrusader at gmail.com - http://binarycrusader.blogspot.com/
On Thu, 2007-04-05 at 22:59 +0200, Jakob Praher wrote:> Hi Cyril, > > thanks for your quick response! > Cyril Plisko wrote: > > On 4/5/07, Jakob Praher <jp at hapra.at> wrote: > >> hi all, > > > >> > >> I am new to solaris. > >> I am creating a zfs filestore which should boot via rootfs. > >> The version of the system is: SunOS store1 5.10 Generic_118855-33 i86pc > >> i386 i86pc. > >> > >> Now I have seen that there is a new rootfs support for solaris starting > >> with build: snv_62. > >> (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) > >> > >> Is it > >> a) possible to start from a raidz pool? > > > > No. At this point raidz pool is not usable as a boot pool. > > > > Is this possible then to use a mirror pool? >Right now, the only supported root filesystem config for ZFS is a (non- striped) mirror or single-disk configuration.> >> b) possible to update my version using a patch from the web to the above > >> version? > > > > Generally speaking there is no patch to get your system from any 5.x > > release > > to 5.x+1 release. You may, however, upgrade your current system from > > SunOS 5.10 to Nevada using regular LiveUpgrade or DeadUpgrade(TM) > > procedure. > > > > (I would just install from scratch - assuming you have all your valuable > > data stored externally or on exportable zpool) > >Unlike may flavors of Linux and *BSD, Solaris does not support live in- place upgrades between releases (e.g. Solaris 10 to Solaris 11). It is similar to the various RPM-based Linux systems that require a boot from an installation media to do the upgrade. However, Solaris also supports something called LiveUpgrade (as Cyril mentioned), where you can upgrade a running system image to a spare parition, then reboot to the new partition to get the new OS.> > So to get this right: > Nevada == Solaris Express?! >Yes, it''s a bit confusing. Think of "Nevada" as a distro name (in Linux terms), which uses the OpenSolaris source base. There are (generally) weekly builds, which is what you will see referred to as "B61". Solaris Express is the marketing name for periodic releases of specific builds of Nevada (so, every couple of months, a build of Nevada is released as "Solaris Express" - it''s for people who want the latest technology,, with _some_ support options, while not living on the absolute bleeding edge like us folks).> This is a little bit confusing. > I am very glad Ian Murdock joined Sun. Hopefully system upgrade will be > as easy as apt-get dist-upgrade. > Is there any easy way to just get the latest solaris kernel via web? > > thanks > JakobBeing able to do a in-place "live" upgrade between releases like with Debian Linux is unlikely to be supported anytime. We''d probably need to change package formats (which, is a whole ''nother ball of wax), plus do a bunch of other work. There is a Debian pkg-based OpenSolaris distro called "Nexenta" (http://www.gnusolaris.org) which you might want to at least look at. Realistically, the only way to update a Nevada installation is to either boot from install media and do an Upgrade Install, or do the LiveUpgrade thing above. There is something called BFU, but I''d avoid that as a newbie. Solaris 10 (the fully supported version) gets periodic back-ports of many new features first done in Nevada (ZFS being a big one). However, there is generally a 6-12 month lag time between something appearing in Nevada and it making it into Solaris 10. Solaris 10 is updated through patches, which are now managed via the Sun Update Connection. I would subscribe to a couple of the support/discuss mailing lists over in the OpenSolaris world (http://www.opensolaris.org/os/discussions/), as this place is pretty much a ZFS-specific place. -- Erik Trimble Java System Support Mailstop: usca14-102 Phone: x17195 Santa Clara, CA Timezone: US/Pacific (GMT-0800)
Erik Trimble wrote:> On Thu, 2007-04-05 at 22:59 +0200, Jakob Praher wrote: >> Hi Cyril, >> >> So to get this right: >> Nevada == Solaris Express?! >> > Yes, it''s a bit confusing. Think of "Nevada" as a distro name (in Linux > terms), which uses the OpenSolaris source base. There are (generally) > weekly builds, which is what you will see referred to as "B61". Solaris > Express is the marketing name for periodic releases of specific builds > of Nevada (so, every couple of months, a build of Nevada is released as > "Solaris Express" - it''s for people who want the latest technology,, > with _some_ support options, while not living on the absolute bleeding > edge like us folks). >The thing is: I am creating a network centered storage server, and for that I''d like to have a somewhat stable OS. I would like to use ZFS and then snapshot to another node (quite freqently) which should give me some DRBD like behavior. IMHO I wanted to have just one giant raidz zfs pool that can be booted from and not bother with the rest. I thought it would be rather hard to support RAIDz as a root pool. Though I gave it a try. Maybe I just should forget the root zfs stuff, if i nonetheless have to use 2 pools in order to have the rest use raidz which is what i need for robustness. Maybe I will just take a hardware raid approach to the root partition (just to have failover support) and to not make the one giant root approach using zfs. One ZFS related question: If I use the ufs partition to boot into the ZFS partition (the "old rootfs" stuff), raidz should then be technically speeking possible? Since in this case grub is using UFS to load the platform kernel and the initial ramdisk? So maybe it should work to have a very small UFS partition mirrored manually on several disks and then to boot into a raidz ZFS. My ZFS partition FAULTED when I tried to boot via UFS on Solaris 10. Is the root fs support mentioned in: http://blogs.sun.com/tabriz/#are_you_ready_to_rumble supported in Solaris 10? Thanks. I am sorry for so much noise on this file system related list. -- Jakob
Hello Erik, Friday, April 6, 2007, 12:45:14 AM, you wrote: ET> On Thu, 2007-04-05 at 22:59 +0200, Jakob Praher wrote:>> Hi Cyril, >> >> thanks for your quick response! >> Cyril Plisko wrote: >> > On 4/5/07, Jakob Praher <jp at hapra.at> wrote: >> >> hi all, >> > >> >> >> >> I am new to solaris. >> >> I am creating a zfs filestore which should boot via rootfs. >> >> The version of the system is: SunOS store1 5.10 Generic_118855-33 i86pc >> >> i386 i86pc. >> >> >> >> Now I have seen that there is a new rootfs support for solaris starting >> >> with build: snv_62. >> >> (http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) >> >> >> >> Is it >> >> a) possible to start from a raidz pool? >> > >> > No. At this point raidz pool is not usable as a boot pool. >> > >> >> Is this possible then to use a mirror pool? >>ET> Right now, the only supported root filesystem config for ZFS is a (non- ET> striped) mirror or single-disk configuration. Are there any plans tyo suppport raid-10 for rootfs? As lot of Sun''s servers have 4 disks in many cases it would be much cleaner/simple to create one raid-10 pool instead of creating another pool. -- Best regards, Robert mailto:rmilkowski at task.gda.pl http://milek.blogspot.com
Robert Milkowski wrote:>Hello Erik, > >Friday, April 6, 2007, 12:45:14 AM, you wrote: > >ET> On Thu, 2007-04-05 at 22:59 +0200, Jakob Praher wrote: > > >>>Hi Cyril, >>> >>>thanks for your quick response! >>>Cyril Plisko wrote: >>> >>> >>>>On 4/5/07, Jakob Praher <jp at hapra.at> wrote: >>>> >>>> >>>>>hi all, >>>>> >>>>> >>>>>I am new to solaris. >>>>>I am creating a zfs filestore which should boot via rootfs. >>>>>The version of the system is: SunOS store1 5.10 Generic_118855-33 i86pc >>>>>i386 i86pc. >>>>> >>>>>Now I have seen that there is a new rootfs support for solaris starting >>>>>with build: snv_62. >>>>>(http://www.opensolaris.org/os/community/zfs/boot/zfsboot-manual/) >>>>> >>>>>Is it >>>>>a) possible to start from a raidz pool? >>>>> >>>>> >>>>No. At this point raidz pool is not usable as a boot pool. >>>> >>>> >>>> >>>Is this possible then to use a mirror pool? >>> >>> >>> > >ET> Right now, the only supported root filesystem config for ZFS is a (non- >ET> striped) mirror or single-disk configuration. > >Are there any plans tyo suppport raid-10 for rootfs? >I don''t know what raid-10 is, but we do have plans to support booting from RAID-Z. The design is still being worked out, but it''s likely that it will involve a new kind of dataset which is replicated on each disk of the RAID-Z pool, and which contains the boot archive and other crucial files that the booter needs to read. I don''t have a projected date for when it will be available. It''s a lower priority project than getting the install support for zfs boot done. Lori -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070406/1f75d776/attachment.html>
eric taylor wrote:>>I don''t know what raid-10 is, but we do have plans to support >>booting from RAID-Z. >> >> > >raid-10 (or raid 1+0) is mirroring plus striping. > > >Thanks, Eric. Also to Malachi, who informed me of this also. I expect that the same "replicate on all disks" dataset property that I''m proposing for booting from RAIDZ would enable us to implement booting from raid-10 too. Lori -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070406/9bbea848/attachment.html>