I had a pool which I created using zfs-fuse, which is using March code base (exact version, I don't know; if someone can tell me the command to find the zpool format version, I would be grateful).
I exported it and now I tried to import it in OpenSolaris, which is running Feb bits because it says 134 Feb 2010 in uname output (2009-06 updated with pkg image-update). It fails to import it because of incompatible version. Backward compatibility is a given and I know Solaris will never compromise on that and Sun has been industry leader in that. What about forward compatibility? I would think zfs pool format would be stable by now. So, what happened here? I know I am going to get shouted at for saying this but this tells me that ZFS is still not on-disk stable in the same vein as BTRFS is not on-disk stable. But it gets better. I can mount and use BTRFS FSs which were created after 2.6.32 (which was a long ago) in a 2.6.32 kernel i.e. I can boot my older kernel if I need to and still access the newer FS and files in it, without breaking anything. Of course, the newer kernels work with FSs created in older kernels. May be I am doing something wrong. May be it is just about using '-f' flag and things will work out and nothing will break. Is it? I look fwd to guidance from the community on this. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
