All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Neil Brown <neilb@suse.de>
Cc: Luca Berra <bluca@comedia.it>, linux-raid@vger.kernel.org
Subject: zeroing old superblocks & upgrading...
Date: Thu, 6 Jul 2006 18:22:31 -0400	[thread overview]
Message-ID: <17581.36135.379062.709693@stoffel.org> (raw)


Neil,

First off, thanks for all your hard work on this software, it's really
a great thing to have.

But I've got some interesting issues here.  Though not urgent.  As
I've said in other messages, I've got a pair of 120gb HDs mirrored.
I'm using MD across partitions, /dev/hde1 and /dev/hdg1.  Works
nicely.

But I see that I have an old superblock sitting around on /dev/hde
(notice, no partition here!) which I'd like to clean up.

    # mdadm -E /dev/hde
    /dev/hde:
	      Magic : a92b4efc
	    Version : 00.90.00
	       UUID : 9835ebd0:5d02ebf0:907edc91:c4bf97b2
      Creation Time : Fri Oct 24 19:11:02 2003
	 Raid Level : raid1
	Device Size : 117220736 (111.79 GiB 120.03 GB)
	 Array Size : 117220736 (111.79 GiB 120.03 GB)
       Raid Devices : 2
      Total Devices : 2
    Preferred Minor : 0

	Update Time : Fri Oct 24 19:21:59 2003
	      State : clean
     Active Devices : 1
    Working Devices : 1
     Failed Devices : 1
      Spare Devices : 0
	   Checksum : 79d2a6fd - correct
	     Events : 0.2


	  Number   Major   Minor   RaidDevice State
    this     0       3        0        0      active sync   /dev/hda

       0     0       3        0        0      active sync   /dev/hda
       1     1       0        0        1      faulty


Here's the correct ones:

    # mdadm -E /dev/hde1
    /dev/hde1:
	      Magic : a92b4efc
	    Version : 00.90.00
	       UUID : 2e078443:42b63ef5:cc179492:aecf0094
      Creation Time : Fri Oct 24 19:23:41 2003
	 Raid Level : raid1
	Device Size : 117218176 (111.79 GiB 120.03 GB)
	 Array Size : 117218176 (111.79 GiB 120.03 GB)
       Raid Devices : 2
      Total Devices : 2
    Preferred Minor : 0

	Update Time : Thu Jul  6 18:21:08 2006
	      State : clean
     Active Devices : 2
    Working Devices : 2
     Failed Devices : 0
      Spare Devices : 0
	   Checksum : 210069e5 - correct
	     Events : 0.7762540


	  Number   Major   Minor   RaidDevice State
    this     0      33        1        0      active sync   /dev/hde1

       0     0      33        1        0      active sync   /dev/hde1
       1     1      34        1        1      active sync   /dev/hdg1


I can't seem to zero it out:

  # mdadm --misc --zero-superblock /dev/hde
  mdadm: Couldn't open /dev/hde for write - not zeroing

Should I just ignore this, or should I break off /dev/hde from the
array and scrub the disk and then re-add it back in?

Also, can I upgrade my superblock to the latest version with out any
problems?

Thanks,
John

             reply	other threads:[~2006-07-06 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 22:22 John Stoffel [this message]
2006-07-06 23:09 ` zeroing old superblocks & upgrading Neil Brown
2006-07-07 13:10   ` John Stoffel
2006-07-17 23:57     ` Neil Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17581.36135.379062.709693@stoffel.org \
    --to=john@stoffel.org \
    --cc=bluca@comedia.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.