From: Tyler <pml@dtbb.net>
To: linux-raid@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: BUGREPORT: mdadm v2.0-devel - Examine and zero-superblock misbehaving
Date: Tue, 03 May 2005 04:02:57 -0700 [thread overview]
Message-ID: <42775A61.6020708@dtbb.net> (raw)
On a site note, mdadm --zero-superblock doesn't seem to work correctly
with mdadm v2.0-devel, it reports no error when you use it, but you can
mdadm -E /dev/hdX after using it, and there is still a superblock, if
you use mdadm v1.9.0-2, it works correctly, and the examine shows
nothing afterwards. Examples follow after the first problem. Mdadm
v2.0 also seems to misreport the findings using the examine function..
"381 spares." Using kernel 2.6.12-rc3-mm2.
First i run zero superblock with mdadm v2.0-devel from current dir:
root@localhost:~/dev/mdadm-2.0-devel-1# ./mdadm --zero-superblock /dev/hdc
Then examine the superblock using mdadm v2.0-devel from current dir:
root@localhost:~/dev/mdadm-2.0-devel-1# ./mdadm -E /dev/hdc
/dev/hdc:
Magic : a92b4efc
Version : 01.00
Array UUID : f4b2dc026e:a3cc3e95:de0563f5:199250
Name :
Creation Time : Tue May 3 11:16:22 2005
Raid Level : raid5
Raid Devices : 3
Device Size : 390721952 (186.31 GiB 200.05 GB)
Super Offset : 390721952 sectors
State : active
Device UUID : f4b2dc026e:a3cc3e95:de0563f5:199250
Update Time : Tue May 3 11:16:22 2005
Checksum : d4cd5d80 - correct
Events : 0
Layout : -unknown-
Chunk Size : 64K
Array State : Uuu 381 spares
Then i try using mdadm v1.9.0 (from system path):
root@localhost:~/dev/mdadm-2.0-devel-1# mdadm --version
mdadm - v1.9.0 - 04 February 2005
root@localhost:~/dev/mdadm-2.0-devel-1# mdadm -E /dev/hdc
mdadm: No super block found on /dev/hdc (Expected magic a92b4efc, got
00000000)
Then i try erasing the superblock again with mdadm v1.9.0 from system path:
root@pink:~/dev/mdadm-2.0-devel-1# mdadm --version
mdadm - v1.9.0 - 04 February 2005
root@pink:~/dev/mdadm-2.0-devel-1# mdadm --zero-superblock /dev/hdc
mdadm: /dev/hdc does not appear to have an MD superblock.
Then examine it again with mdadm v2.0-devel from current dir:
root@pink:~/dev/mdadm-2.0-devel-1# ./mdadm -E /dev/hdc
/dev/hdc:
Magic : a92b4efc
Version : 01.00
Array UUID : f4b2dc026e:a3cc3e95:de0563f5:199250
Name :
Creation Time : Tue May 3 11:16:22 2005
Raid Level : raid5
Raid Devices : 3
Device Size : 390721952 (186.31 GiB 200.05 GB)
Super Offset : 390721952 sectors
State : active
Device UUID : f4b2dc026e:a3cc3e95:de0563f5:199250
Update Time : Tue May 3 11:16:22 2005
Checksum : d4cd5d80 - correct
Events : 0
Layout : -unknown-
Chunk Size : 64K
Array State : Uuu 381 spares
next reply other threads:[~2005-05-03 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 11:02 Tyler [this message]
2005-05-03 23:50 ` BUGREPORT: mdadm v2.0-devel - Examine and zero-superblock misbehaving Neil Brown
2005-05-03 23:55 ` Tyler
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=42775A61.6020708@dtbb.net \
--to=pml@dtbb.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).