Commit 07480bb5 authored by Mike Hibler's avatar Mike Hibler
Browse files

For the DDF 2.0 RAID standard, we need to zap up to 32MB at the end of disk.

Turns out the Linux raid tool (mdadm) will pick up fragmentary RAID
metadata and complain mightily.
parent 48f4a757
* Copyright (c) 2005-2016 University of Utah and the Flux Group.
* Copyright (c) 2005-2017 University of Utah and the Flux Group.
......@@ -45,11 +45,13 @@
* For FS superblocks and other metadata we wipe the first 4M since that
* is sufficient to wipe the most commonly sized LVM metadata block.
* For boot blocks we need up to 32k for GPT.
* For certain HW/SW RAID standards, we may need to zap even more (up to
* 32MB for DDF 2.0) at the end of the disk.
#define MD_ZAPSIZE (4*1024*1024)
#define MD_ZAPSIZE (32*1024*1024)
#define MBR_ZAPSIZE 512
#define GPT_ZAPSIZE (32*1024)
#define MAX_ZAPSIZE (4*1024*1024)
#define MAX_ZAPSIZE (32*1024*1024)
static int verbose = 0;
static int pnum = 0;
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment