Date: Fri, 5 Apr 2013 15:13:02 -0700 (PDT) From: Beeblebrox <zaphod@berentweb.com> To: freebsd-questions@freebsd.org Subject: [ZFS] recover destroyed zpool - what are the available options? Message-ID: <1365199982331-5801834.post@n5.nabble.com> In-Reply-To: <1365160406005-5801734.post@n5.nabble.com> References: <515C4B14.80300@gmail.com> <1365004246715-5801356.post@n5.nabble.com> <1365087055.99393.YahooMailRC@web184303.mail.ne1.yahoo.com> <1365090630957-5801568.post@n5.nabble.com> <1365091829108-5801581.post@n5.nabble.com> <1365092775955-5801588.post@n5.nabble.com> <515E8BDF.9070403@gmail.com> <1365152049024-5801716.post@n5.nabble.com> <515EAABF.6020300@gmail.com> <1365160406005-5801734.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I think I might have a better understanding of the situation. 'zpool status' and 'zdb -C' commands both show bsdr properties as: pool_guid: 17852168552651762162 children[0]: \ type: 'disk' \ guid: 12606749387939346898 Whereas 'zpool import -D' and 'zdb -l' commands give the bsdr properties as: pool_guid: 12018916494219117471 vdev_tree: \ type: 'disk \ top_guid: 17860002997423999070 Since the LABEL info on the HDD is the more relevant data, I should be using the output of zdb -l, and disregard the pool that shows itself as "already imported - albeit faulted". I therefore plan to import the bsdr pool with a newname and should run the import command as: zpool import -D -f -R /bsdr -N -F -n -X 12018916494219117471 newname Any objections? We must also keep in mind that '-D' flag is showing TWO deleted bsdr pools, so I must use the unique ID. Please let me know if I should go ahead and run above command. Thanks and Regards. -- View this message in context: http://freebsd.1045724.n5.nabble.com/ZFS-recover-destroyed-zpool-what-are-the-available-options-tp5800299p5801834.html Sent from the freebsd-questions mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1365199982331-5801834.post>