No, not an issue :-)
This is just a thank you note to the ZFS team and all contributors that worked
hard to deliver ZFS boot support in snv_90. ZFS is a great achievement for
Solaris and operating systems in general, and I believe ZFS boot will make the
lives of many, many computer users much
I'm afraid I asked a very stupid question...
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
I'm afraid the Solaris installer won't let me stop the process just before it
starts copying files to the target filesystem. It would be very nice to get
away with the UFS slice altogether, but between filesystem creation and
initialisation (which seems mandatory) and copying there is no pause
Hi,
This is a report of my latest investigations on how to setup (by hand) your ZFS
root filesystem.
My experiment was carried on with Solaris Express Community Edition b66 DVD and
an additional disk slice to temporarily install the root fs to. It takes place
during the installation process as
No. There is nothing else the OS can do when it
cannot mount the root
filesystem.
I have the impression (didn't check though) that the pool is made available by
just setting some information in its main superblock or something alike (sorry
for the imprecisions in ZFS jargon). I understand
Now that I know *what*, could you perhaps explain
to my *why*? I understood zpool import and export
operations much as mount and unmount, like maybe some
checks on the integrity of the pool and updates to
some structure on the OS to maintain the
imported/exported state of that pool. But now
Once you switch over to zfs root, adding new hardware
should just behave
as what you expect on ufs root.
Copy /devices and /dev is just a one-time thing (as
part of
'installation') to setup the initial zfs root.
Ok, but what about the first boot? Why can't /devices and /dev be generated
Hi Lin,
A few moments after replying to your post, I had an idea. I had tweaked with
almost every part of the script but I couldn't figure out what the difference
was between the script and the manual execution.
The difference is (as I found later) that when I created the ZFS root fs by
Hi Doug,
I need more information:
You need /devices and /dev on zfs root to boot.
Right. But can I generate them automatically somehow on the next boot? I have
followed the instructions that loop-mount / and tar the contents of devices and
dev and untar them to the root pool. I just want
Hi Doug, from the information I read so far, I assume
you have
c0d0s0 - ufs root
c0d0s5 - zfs root pool 'snv' and root filesystem
'b65'
Hi Lin,
My complete layout follows:
c0d0s0: boot slice (holds a manually maintained /boot) -- UFS
c0d0s1: the usual swap slice
c0d0s3: S10U3 root --
Hi,
I have been trying to setup a boot ZFS filesystem since b63 and found out about
bug 6553537 that was preventing boot from ZFS filesystems starting from b63.
First question is whether b65 has solved the problem as was planned on the bug
page. Second question is: as I cannot boot successfully
11 matches
Mail list logo
