Gareth Howell writes: >>>> I rebooted in to recovery mode and swapped the pools as suggested. The >>>> system now boots using the new ones pool but it fails to start the local >>>> file system service and all those that rely on it. >>>> The cause is some cruft in the /zones folder that prevents /zones mounting. >>> >>> Strangely enough, I did something quite similar last weekend. I moved >>> the zones pool from one disk to another using zfs send/receive. Every- >>> thing was copied *except* the mointpoint of the zones pool itself. >>> >>> Once I found out it was set to "none", I set it to "/zones", and all >>> was fine. >> OK, I got to the bottom of the problem. It was caused by the old pool still being connected.
When I powered on, it seems that Smartos mounts the pools in alphabetical order. Thus the datasets in ‘oldzones’ mounted before ‘zones’ got a chance to nab the various mount points on /zones. Rather than go through and change all the mountpoints on the ‘oldzones’ pool, I simply pulled the disk before powering on. All running OK now and I can repeat the process on the main server (this was a test run using the backup server). Gareth
signature.asc
Description: Message signed with OpenPGP
------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
