I have a pool that I created on Solaris 10 originally. I placed about 35 GB of files in the root file system. After importing the pool into Linux through the latest KQ rpms, everything seemed great. I created some more test file systems (on Linux), and then exported the file system. I then wanted to test if I could go back and forth between Linux and Solaris (this is on a SAN), and at first things seemed great. Back in Solaris I copied some 20 GB of files to the new file systems I created on Linux. After exporting the pool and importing into Linux, none of the new files I copied show up! zfs list reports the file systems are empty. Importing the pool back into Solaris, and solaris also reports the file systems are empty.
Solaris 10u6 obviously has an older version of ZFS and zpool. But not being able to to go back and forth between Linux (if contingencies arise) is a very serious problem for me. I don't mind using an older on-disk format for pools and ZFS for now--when I've migrated entirely to Linux I can upgrade them.
So the question is, is what I experienced a serious bug, or just a massive incompatibility between the latest version of ZFS (opensolaris) and the version my Solaris 10u6 machine uses? If ZFS on Linux is to be a successful migration path for me, I need to have in the short term the ability to go back to Solaris 10 if something bad happens.
I have a pool that I created on Solaris 10 originally. I placed about 35 GB of files in the root file system. After importing the pool into Linux through the latest KQ rpms, everything seemed great. I created some more test file systems (on Linux), and then exported the file system. I then wanted to test if I could go back and forth between Linux and Solaris (this is on a SAN), and at first things seemed great. Back in Solaris I copied some 20 GB of files to the new file systems I created on Linux. After exporting the pool and importing into Linux, none of the new files I copied show up! zfs list reports the file systems are empty. Importing the pool back into Solaris, and solaris also reports the file systems are empty.
Solaris 10u6 obviously has an older version of ZFS and zpool. But not being able to to go back and forth between Linux (if contingencies arise) is a very serious problem for me. I don't mind using an older on-disk format for pools and ZFS for now--when I've migrated entirely to Linux I can upgrade them.
So the question is, is what I experienced a serious bug, or just a massive incompatibility between the latest version of ZFS (opensolaris) and the version my Solaris 10u6 machine uses? If ZFS on Linux is to be a successful migration path for me, I need to have in the short term the ability to go back to Solaris 10 if something bad happens.