ZFS migration - New pool lost after reboot

[sebastian at wolfgarten.com]

Dear Kevin,

thanks a lot for your follow-up. Indeed the -N option solved my dilemma.

Best regards
Sebastian

Am 2016-05-04 15:03, schrieb Kevin P. Neal:
> On Tue, May 03, 2016 at 11:07:35PM +0200, Sebastian Wolfgarten wrote:
>> Dear all,
>> 
>> thanks to Matthias I already fixed most of the issues but there is one 
>> thing I cannot fix yet. When trying to set the mount point for the / 
>> file system, I am getting strange errors:
>> 
>> root at vm:~ # zfs set mountpoint=none newpool/ROOT
>> cannot open 'newpool/ROOT': dataset does not exist
>> root at vm:~ # zpool import -c /tmp/newpool.cache -R /mnt newpool
>> root at vm:~ # zfs set mountpoint=none newpool/ROOT
>> cannot unmount '/mnt': Device busy
>> root at vm:~ # zfs set mountpoint=/ newpool/ROOT/default
>> cannot unmount '/mnt': Device busy
>> root at vm:~ # zfs set mountpoint=/tmp newpool/tmp
>> root at vm:~ # zfs set mountpoint=/usr newpool/usr
>> root at vm:~ # zfs set mountpoint=/var newpool/var
>> root at vm:~ # zfs set mountpoint=none newpool/ROOT
>> cannot unmount '/mnt': Device busy
>> root at vm:~ # zpool export newpool
>> root at vm:~ # zfs set mountpoint=none newpool/ROOT
>> cannot open 'newpool/ROOT': dataset does not exist
>> 
>> So basically, when the pool is not mounted the system says „dataset 
>> does not exist“ but when I mount it and try to change the mount point 
>> it comes back with „Device busy“. Any ideas on how I am supposed to 
>> set the mount point for the root file system (first & last line of the 
>> commands listed above)?
> 
> There's a middle ground you left out of your analysis.
> 
> You can import a pool and not mount it. Use the "-N" option to zfs 
> import.