On Fri, Nov 7, 2014 at 10:05 AM, Josef 'Jeff' Sipek via illumos-zfs < [email protected]> wrote:
> I'm trying to figure out sort of a self-inflicted assertion in zdb. This > lead me to two questions for which I didn't find an obvious answer: > > (1) why does zdb import pools read-write? E.g., > > libzpool.so.1`spa_import+0x48d(8072c430, 8072c440, 0, 4) > main+0x611(3, fffffd7fffdffd08) > _start+0x6c() > zdb does everything readonly: kernel_init(FREAD); so even if you don't pass readonly=true in the props, you won't be able to write to the pool. > > (2) at what point during/after import is it safe to issue sync tasks? (The > code I'm dealing with tries to at the end of spa_import.) > Not sure that is the best place to do it, but it should work. (Assuming this is at the very end of spa_import(), after the namespace lock is dropped.) > > Thanks, > > Jeff. > > -- > Once you have their hardware. Never give it back. > (The First Rule of Hardware Acquisition) > > > ------------------------------------------- > illumos-zfs > Archives: https://www.listbox.com/member/archive/182191/=now > RSS Feed: > https://www.listbox.com/member/archive/rss/182191/21635000-ebd1d460 > Modify Your Subscription: > https://www.listbox.com/member/?member_id=21635000&id_secret=21635000-73dc201a > Powered by Listbox: http://www.listbox.com >
_______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
