ZFS migration - New pool lost after reboot
Sebastian Wolfgarten
sebastian at wolfgarten.com
Tue May 3 21:07:49 UTC 2016
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)?
Many thanks.
Kind regards
Sebastian
> Am 02.05.2016 um 23:45 schrieb Matthias Fechner <idefix at fechner.net>:
>
> Am 02.05.2016 um 22:42 schrieb Sebastian Wolfgarten:
>> root at vm:~ # zfs list
>> NAME USED AVAIL REFER MOUNTPOINT
>> newpool 385M 5.41G 19K /mnt/zroot
>> newpool/ROOT 385M 5.41G 19K /mnt
>> newpool/ROOT/default 385M 5.41G 385M /mnt
>> newpool/tmp 21K 5.41G 21K /mnt/tmp
>> newpool/usr 76K 5.41G 19K /mnt/usr
>> newpool/usr/home 19K 5.41G 19K /mnt/usr/home
>> newpool/usr/ports 19K 5.41G 19K /mnt/usr/ports
>> newpool/usr/src 19K 5.41G 19K /mnt/usr/src
>> newpool/var 139K 5.41G 19K /mnt/var
>> newpool/var/audit 19K 5.41G 19K /mnt/var/audit
>> newpool/var/crash 19K 5.41G 19K /mnt/var/crash
>> newpool/var/log 44K 5.41G 44K /mnt/var/log
>> newpool/var/mail 19K 5.41G 19K /mnt/var/mail
>> newpool/var/tmp 19K 5.41G 19K /mnt/var/tmp
>> zroot 524M 26.4G 96K /zroot
>> zroot/ROOT 522M 26.4G 96K none
>> zroot/ROOT/default 522M 26.4G 522M /
>> zroot/tmp 74.5K 26.4G 74.5K /tmp
>> zroot/usr 384K 26.4G 96K /usr
>> zroot/usr/home 96K 26.4G 96K /usr/home
>> zroot/usr/ports 96K 26.4G 96K /usr/ports
>> zroot/usr/src 96K 26.4G 96K /usr/src
>> zroot/var 580K 26.4G 96K /var
>> zroot/var/audit 96K 26.4G 96K /var/audit
>> zroot/var/crash 96K 26.4G 96K /var/crash
>> zroot/var/log 103K 26.4G 103K /var/log
>> zroot/var/mail 96K 26.4G 96K /var/mail
>> zroot/var/tmp 92.5K 26.4G 92.5K /var/tmp
>>
>> I am assuming I have to amend the zfs parameters for the mount points but I can’t seem to figure out what’s wrong. I tried things like:
>>
>> zfs set mountpoint=/usr newpool/usr
>> zfs set mountpoint=/tmp newpool/tmp
>> zfs set mountpoint=/var newpool/var
>
> zfs set mountpoint=none newpool/ROOT
> zfs set mountpoin=/ newpool/ROOT/default
> zfs set mountpoin=/tmp newpool/tmp
> zfs set mountpoin=/usr newpool/usr
> zfs set mountpoin=/var newpool/var
>
>
> Gruß
> Matthias
>
> --
>
> "Programming today is a race between software engineers striving to
> build bigger and better idiot-proof programs, and the universe trying to
> produce bigger and better idiots. So far, the universe is winning." --
> Rich Cook
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions
mailing list