Re: [zfs-discuss] lucreate error: Cannot determine the physical

2008-04-09 Thread Roman Morokutti
Support will become available in the build 89 or 90 time frame, at the same time that zfs as a root file system is supported. I greatly appreciate this and there is nothing more to do than to wait for zfs being capable of live upgrading. Roman This message posted from opensolaris.org

[zfs-discuss] lucreate error: Cannot determine the physical boot device ...

2008-04-08 Thread Roman Morokutti
# lucreate -n B85 Analyzing system configuration. Hi, after typing # lucreate -n B85 I get the following error: No name for current boot environment. INFORMATION: The current boot environment is not named - assigning name BE1. Current boot environment is named BE1. Creating initial

Re: [zfs-discuss] lucreate error: Cannot determine the physical boot device ...

2008-04-08 Thread Roman Morokutti
I further found out that there exists a nearly similar problem described in Bug-Id: 6442921. lubootdev reported: # /etc/lib/lu/lubootdev -b /dev/dsk/c0d0p0 Using this info for -C I got the following: # lucreate -C /dev/dsk/c0d0p0 -n B85 Analyzing system configuration. No name for current boot

Re: [zfs-discuss] lucreate error: Cannot determine the physical

2008-04-08 Thread Roman Morokutti
I didn't think that we had live upgrade support for zfs root filesystem yet. Original quote from Lori Alt: ZFS is ideally suited to making “clone and modify” fast, easy, and space-efficient. Both “clone and modify” tools will work much better if your root file system is ZFS. (The new install

Re: [zfs-discuss] Is swap still needed on c0d0s1 to get crash dumps?

2008-02-11 Thread Roman Morokutti
Thank you for your info. So with dumpadm I can manage crash-dumps. And if ZFS is not capable of handling those dumps, who cares. Then I will create an extra slice for those purposes. No problem. Roman This message posted from opensolaris.org ___

[zfs-discuss] Is swap still needed on c0d0s1 to get crash dumps?

2008-02-07 Thread Roman Morokutti
Lori Alt writes in the netinstall README that a slice should be available for crash dumps. In order to get this done the following line should be defined within the profile: filesys c0[t0]d0s1 auto swap So my question is, is this still needed and how to access a crash dump if it happened?

Re: [zfs-discuss] status of zfs boot netinstall kit

2008-02-06 Thread Roman Morokutti
Hi, I would like to continue this (maybe a bit outdated) thread with the question: 1. How to create a netinstall image? 2. How to write the netinstall image back as an ISO9660 on DVD? (after patching it for the zfsboot) Roman This message posted from opensolaris.org

Re: [zfs-discuss] How to get ZFS use the whole disk?

2008-02-04 Thread Roman Morokutti
Just another thought. After setting up a ZFS root on slice c0d0s4, it should be just possible after starting into it, to add the remaining slices into the created ZFS pool. Is this possible? Roman This message posted from opensolaris.org ___

[zfs-discuss] How to get ZFS use the whole disk?

2008-02-01 Thread Roman Morokutti
Hi, I am new to ZFS and recently managed to get a ZFS root to work. These were the steps I have done: 1. Installed b81 (fresh install) 2. Unmounted /second_root on c0d0s4 3. Removed /etc/vfstab entry of /second_root 4. Executed ./zfs-actual-root-install.sh c0d0s4 5. Rebooted (init 6) After

Re: [zfs-discuss] ZFSboot : Initial disk layout

2007-11-27 Thread Roman Morokutti
Hi, thank you for your info. The netinstall would fit perfectly. The following text out from the README does prevent me from using it yet: Although this is not enforced yet, it is likely the required convention for dataset name will be this. pool-name/boot-environment-name[/directory in