That is a touch misleading. This has always been the case since S10u2. You have to create the pool AND the file systems at the oldest versions you want to support.
I maintain a table of pool and version numbers on my blog (blogs.oracle. com/bobn) for this very purpose. I got lazy the other day and made this mistake between 11ga and 11.1. Watch the ZFS send approach because you might be sending a newer file system version than is supported. Yes, I've done that too :) Bob Sent from my iPhone On Dec 13, 2012, at 10:47 AM, Jan Owoc <jso...@gmail.com> wrote: > Hi, > > On Thu, Dec 13, 2012 at 9:14 AM, sol <a...@yahoo.com> wrote: >> Hi >> >> I've just tried to use illumos (151a5) import a pool created on solaris >> (11.1) but it failed with an error about the pool being incompatible. >> >> Are we now at the stage where the two prongs of the zfs fork are pointing in >> incompatible directions? > > Yes, that is correct. The last version of Solaris with source code > used zpool version 28. This is the last version that is readable by > non-Solaris operating systems FreeBSD, GNU/Linux, but also > OpenIndiana. The filesystem, "zfs", is technically at the same > version, but you can't access it if you can't access the pool :-). > > If you want to access the data now, your only option is to use Solaris > to read it, and copy it over (eg. with zfs send | recv) onto a pool > created with version 28. > > Jan > _______________________________________________ > zfs-discuss mailing list > firstname.lastname@example.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list email@example.com http://mail.opensolaris.org/mailman/listinfo/zfs-discuss