On Jul 4, 2010, at 1:33 AM, R. Eulenberg wrote: > R. Eulenberg <ron2105 <at> web.de> writes: > >> >>>> op> I was setting up a new systen (osol 2009.06 >>> and updating to >>>> op> the lastest version of osol/dev - snv_134 - >>> with >>>> op> deduplication) and then I tried to import my >>> backup zpool, but >>>> op> it does not work. >>>> >>>> op> # zpool import -f tank1 >>>> op> cannot import 'tank1': one or more devices >>> is currently unavailable >>>> op> Destroy and re-create the pool from a backup >>> source >>>> >>>> op> Any other option (-F, -X, -V, -D) and any >>> combination of them >>>> op> doesn't helps too. >> >>>> R., please let us know if the 'zdb -e -bcsvL >>> <zpool-name>' incantation >>>> Sigbjorn suggested ends up working for you or not. >> >> Hi, >> >> it seems that you are talking about my case of trouble. >> I answered in this thread: >> >> http://www.opensolaris.org/jive/thread.jspa?messageID=485342&tstart=0#485342 >> >> I hope of any ideas helping me. >> >> Regards >> Ron > > > Hi, > > several days ago I added this: > > set /zfs/:zfs_recover=/1/ > set aok=/1/ > > to the /etc/system file and ran: > > zdb -e -bcsvL tank1 >
settings in the /etc/systm file do not affect zdb in any way. In recent builds (135+) there's an option -A for zdb that allows to simulate setting one or both of these parameters, but anyway it is not useful in your case. > without an output and without a prompt (prozess hangs up) How did you arrive at this conclusion? Did you check "pstack `pgrep zdb`/1" output a few times? > and result of running: > > zdb -eC tank1 > > was the same. > I hope you could help me because the problem isn't solved. > > Regards > Ron > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
