OK, I was careless and "wiped" a disk that I shouldn't have. I also wrote a 0 Byte file to the new volume as well. Is there any hope of data recovery?
Can someone tell me how much of the disk actually gets wiped when you use the GUI to create a new ZFS volume and it prompts you to wipe the disk? (and you stupidly tell it to go through with it)?
I'm hoping it's just partial (maybe the front and back of the disk). I read that someone was able to do ZFS data recovery under a given scenario (which may not be as bad as my situation): http://mbruning.blogspot.com/2009/12/zfs-data-recovery.html
I tried to find where the wipe is done in code by googling "freenas wipe", and it did pull up the changeset for when this feature was originally introduced (http://support.freenas.org/changeset/11454/freenas). Looks like one or more dd commands were used (I don't know Python, so I may have made a mess of these):
That came out of trunk/gui/freeadmin/static/lib/js/freeadmin.js, but the latest freeadmin.js doesn't have any dd commands in it.
For reference, I used FreeNAS-8.3.0-BETA1-x64 to create the new volume on the disk I shouldn't have.
The disk that was wiped contained data written with FreeNAS-8.0.2-RELEASE-amd64 (8288).
I also saw the dd command referenced in the FAQ: http://protosd.blogspot.com/2011/12/protosds-unofficial-freenas-8-faq.html
Is that what is used by the GUI in FreeNAS-8.3.0-BETA1-x64, i.e.
??
Can someone tell me how much of the disk actually gets wiped when you use the GUI to create a new ZFS volume and it prompts you to wipe the disk? (and you stupidly tell it to go through with it)?
I'm hoping it's just partial (maybe the front and back of the disk). I read that someone was able to do ZFS data recovery under a given scenario (which may not be as bad as my situation): http://mbruning.blogspot.com/2009/12/zfs-data-recovery.html
I tried to find where the wipe is done in code by googling "freenas wipe", and it did pull up the changeset for when this feature was originally introduced (http://support.freenas.org/changeset/11454/freenas). Looks like one or more dd commands were used (I don't know Python, so I may have made a mess of these):
Code:
"dd if=/dev/zero of=/dev/%s bs=1m oseek=%s" % (devname, size*1024 - 4) "dd if=/dev/zero of=/dev/%s bs=1m oseek=%s" % (devname, size / 1024 - 4, ) "dd if=/dev/zero of=/dev/%s bs=1m count=1" % (devname, )
That came out of trunk/gui/freeadmin/static/lib/js/freeadmin.js, but the latest freeadmin.js doesn't have any dd commands in it.
For reference, I used FreeNAS-8.3.0-BETA1-x64 to create the new volume on the disk I shouldn't have.
The disk that was wiped contained data written with FreeNAS-8.0.2-RELEASE-amd64 (8288).
I also saw the dd command referenced in the FAQ: http://protosd.blogspot.com/2011/12/protosds-unofficial-freenas-8-faq.html
Is that what is used by the GUI in FreeNAS-8.3.0-BETA1-x64, i.e.
Code:
dd if=/dev/zero of=/dev/ada1 bs=1m count=1 dd if=/dev/zero of=/dev/ada1 bs=1m oseek=`diskinfo ada1 | awk '{print int($3 / (1024*1024)) - 4;}'`
??