On 6/30/14 13:41 , Nigel Magnay via smartos-discuss wrote: > Hi > > I have previously migrated another smartos box to linux without issue, but > I'm having some troubles with our main host. > > Firstly, my pool is complaining about errors that were in zones/dump - > basically exactly as described here: > http://comments.gmane.org/gmane.os.smartos.general/83 > > (I.E: I have 'permanent errors have been detected in the following files: > <0x28>:<0x1>).
The quickest solution to this is destroy and recreate the dump device. > More pressingly, when I try to import into zfs-on-linux, I get a complaint > about the missing feature com.joyent:multi_vdev_crash_dump. > > Of course, I don't care about ever seeing the contents of zones/dump, so if > I could remove it altogether that would be fine. But I don't know whether > that would be sufficient to get the pool to import.. > > What's my shortest route to persuading a non-illumos host to import this > pool? I'm really hoping I don't have to find somewhere to dump *terrabytes* > of ZFS data, and then stream it all back again simply because of a feature > bit... You'll probably have better luck getting the details on the primary zfs list. I'd presume that if you deleted the dump device, you'd be able to disable the feature, but I've never gone down that path before. Assuming the feature is disabled, I don't know of any reason why an import wouldn't work, but again I haven't spent much time in this part of the code base to know about what gotchas do or do not exist here. Alternatively, you could also figure out why the feature bit is missing from zfs-on-linux. Hope this helps, Robert ------------------------------------------- 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
