The history is quite simple: 1) Installed nv_b32 or around there on a zeroed drive. Created this ZFS pool for the first time. 2) Non-live upgraded to nv_b42 when it came out, zpool upgrade on the zpool in question from v2 to v3. 3) Tried to non-live upgrade to nv_b44, upgrade failed every time, so I just blew away my existing partition scheme and install nv_b44 cleanly. 4) Problem begins.
I can't think of any sane reason I could have blown away that directory accidentally, so I don't know. - Rich On 9/22/06, Eric Schrock <[EMAIL PROTECTED]> wrote:
On Fri, Sep 22, 2006 at 03:36:36AM -0400, Rich wrote: > ...huh. > > So /etc/zfs doesn't exist. At all. > > Creating /etc/zfs using mkdir, then importing the pool with zpool > import -f, then rebooting, the behavior vanishes, so...yay. > > Problem solved, I guess, but shouldn't ZFS be smarter about creating > its own config directory? That seems a reasonable RFE, but I wonder how you got into this situation in the first place. What is the history of the OS on this system? Nevada? Solaris 10? Upgraded? Patched? I assume that you don't tend to go around removing random /etc directories on purpose, so I want to make sure that our software didn't screw up somehow. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
-- Friends don't let friends use Internet Explorer or Outlook. Choose something better. www.mozilla.org www.getfirefox.com www.getthunderbird.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
