Well, if I remember correctly "rc_toggle_basic" was the thing to use before "priv set" existed....
/Mats
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Sphar, Mike Sent: den 15 februari 2006 23:42 To: toasters@mathworks.com Subject: wiping disks on an old F230
We've got an old F230 that I was finally able to decommission today, and I figure even though I've deleted all the data it would probably be a good idea to scrub the disks a bit for security purposes.
Problem is I just can't remember (and can't seem to find searching around NOW) what the best way to do that back in OnTap 5.3.7R3D18 was. I know I could do disk sanitize now, but not sure what if anything was available in older versions. Any suggestions?
(I fully concede that I might be having a complete brain failure about the painfully obvious solution I should already know. But I even searched around NOW a bit and couldn't find an answer.)
-- Michael W. Sphar - IS&T - Lead Systems Administrator SMBU Engineering Support Services, BMC Software
I don't belive spares_zero acutally overwrites data, or initalize all disks (option 4 at 22/7 menu). That's why the sanitize commands were created in the first place.
I'm not sure what a good answer is for you. Maybe a bulk magnetic tape eraser? How about attach the shelves locally to a pc, and write a bunch of garbage to it 7 times?
-Blake
On 2/16/06, Mats.Oberg@tietoenator.com Mats.Oberg@tietoenator.com wrote:
Well, if I remember correctly "rc_toggle_basic" was the thing to use before "priv set" existed....
/Mats
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Sphar, Mike Sent: den 15 februari 2006 23:42 To: toasters@mathworks.com Subject: wiping disks on an old F230
We've got an old F230 that I was finally able to decommission today, and I figure even though I've deleted all the data it would probably be a good idea to scrub the disks a bit for security purposes.
Problem is I just can't remember (and can't seem to find searching around NOW) what the best way to do that back in OnTap 5.3.7R3D18 was. I know I could do disk sanitize now, but not sure what if anything was available in older versions. Any suggestions?
(I fully concede that I might be having a complete brain failure about the painfully obvious solution I should already know. But I even searched around NOW a bit and couldn't find an answer.)
-- Michael W. Sphar - IS&T - Lead Systems Administrator SMBU Engineering Support Services, BMC Software
thelastman@gmail.com (Blake Golliher) writes
I don't belive spares_zero acutally overwrites data, or initalize all disks (option 4 at 22/7 menu). That's why the sanitize commands were created in the first place.
spares_zero definitely zeroes the disks, or at least those parts of them that would take part in a raid array (remembering "right sizing" and so on). As it's a single write pass with predictable data it's certainly not erasing to military security standards [*], but it may well be good enough in many situations, e.g. decomissioned discs being passed around within a single organisation.
_Way_ back, before there was even a spares_zero command, I used to boot from floppy and build a new filing system on the filer from scratch, and then add _all_ the disks to it (no hot spares!). The disks are zeroed as they are added to the raid arrays. That method will still work as well.
[*] ... but tehn the algorithm used by "sanitize" would probably not be considered secure enough by the truely paranoid, either!
I don't belive spares_zero acutally overwrites data,
It does.
Proof: Adding a 'zeroed-out' disk to an aggr/trad_volume takes just a few seconds.
Why? -> Because the filer *knows* that the disk is filled with \0's so the parity-disk does not have to care about the new disk.
Or maybe, it just unallocated those blocks, and says "that data there? just ignore it". Which to me is more likely.
-Blake
On 2/17/06, Adrian Ulrich toaster@blinkenlights.ch wrote:
I don't belive spares_zero acutally overwrites data,
It does.
Proof: Adding a 'zeroed-out' disk to an aggr/trad_volume takes just a few seconds.
Why? -> Because the filer *knows* that the disk is filled with \0's so the parity-disk does not have to care about the new disk.
If it didn't actually zero out the data then parity/data reconstruction for failed disks would not work - you'd end up with garbage since blocks that parity though were zero were actually not.
Simon.
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Blake Golliher Sent: Friday, February 17, 2006 10:15 PM To: Adrian Ulrich Cc: toasters@mathworks.com Subject: Re: wiping disks on an old F230
Or maybe, it just unallocated those blocks, and says "that data there? just ignore it". Which to me is more likely.
-Blake
On 2/17/06, Adrian Ulrich toaster@blinkenlights.ch wrote:
I don't belive spares_zero acutally overwrites data,
It does.
Proof: Adding a 'zeroed-out' disk to an aggr/trad_volume takes just a few seconds.
Why? -> Because the filer *knows* that the disk is filled with \0's so the parity-disk does not have to care about the new disk.
-
Adrian Ulrich -
Blake Golliher -
Chris Thompson -
Mats.Oberg＠tietoenator.com -
Simon Ferrett