From: Marco De Vitis <starless@spin.it>
To: linux-raid@vger.kernel.org
Subject: mdadm and size differences
Date: Tue, 24 Nov 2015 11:32:33 +0100 [thread overview]
Message-ID: <n31ec1$ebi$1@ger.gmane.org> (raw)
Hi,
I cannot understand a difference in size I can see on an old Debian 5.0
machine, maybe I'm just missing something obvious.
/dev/sdd is partitioned as follows, and /dev/sdf is exactly the same:
> #>fdisk -l /dev/sdd
>
> Disk /dev/sdd: 500.1 GB, 500107862016 bytes
> 255 heads, 63 sectors/track, 60801 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x000901d8
>
> Device Boot Start End Blocks Id System
> /dev/sdd1 1 24 192748+ 83 Linux
> /dev/sdd2 25 60801 488191252+ 5 Extended
> /dev/sdd5 25 632 4883728+ 83 Linux
> /dev/sdd6 633 2982 18876343+ 83 Linux
> /dev/sdd7 2983 4199 9775521 83 Linux
> /dev/sdd8 4200 4807 4883728+ 83 Linux
> /dev/sdd9 4808 5173 2939863+ 82 Linux swap / Solaris
> /dev/sdd10 5174 31281 209712478+ 83 Linux
You can see that sdd6 is twice the size of sdd7.
cfdisk reports sizes of around 20 GB and 10 GB:
sdd6 -> 19329.41
sdd7 -> 10010.17
All partitions in these two identical drives are configured as RAID 1
using mdadm, but the md devices associated to sdd6/sdf6 and sdd7/sdf7
are both reported to be 10 GB in size, as can be seen from the mdadm
output below.
Why?
Thanks for any info.
> #>mdadm -vv --detail /dev/md2
> /dev/md2:
> Version : 00.90
> Creation Time : Thu Feb 22 16:18:11 2007
> Raid Level : raid1
> Array Size : 9767424 (9.31 GiB 10.00 GB)
> Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
> Raid Devices : 2
> Total Devices : 2
> Preferred Minor : 2
> Persistence : Superblock is persistent
>
> Update Time : Mon Nov 23 14:19:23 2015
> State : clean
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> UUID : 5582dad7:7ac89883:0c2b9e1d:5009dd35
> Events : 0.69228
>
> Number Major Minor RaidDevice State
> 0 8 54 0 active sync /dev/sdd6
> 1 8 86 1 active sync /dev/sdf6
>
> #>mdadm -vv --detail /dev/md3
> /dev/md3:
> Version : 00.90
> Creation Time : Thu Feb 22 16:18:54 2007
> Raid Level : raid1
> Array Size : 9767424 (9.31 GiB 10.00 GB)
> Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
> Raid Devices : 2
> Total Devices : 2
> Preferred Minor : 3
> Persistence : Superblock is persistent
>
> Update Time : Mon Nov 23 14:19:27 2015
> State : clean
> Active Devices : 2
> Working Devices : 2
> Failed Devices : 0
> Spare Devices : 0
>
> UUID : e44836cf:6340f7fa:52fb3562:a78d4dbb
> Events : 0.187630
>
> Number Major Minor RaidDevice State
> 0 8 55 0 active sync /dev/sdd7
> 1 8 87 1 active sync /dev/sdf7
--
Ciao,
Marco.
next reply other threads:[~2015-11-24 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 10:32 Marco De Vitis [this message]
2015-12-21 2:32 ` mdadm and size differences NeilBrown
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='n31ec1$ebi$1@ger.gmane.org' \
--to=starless@spin.it \
--cc=linux-raid@vger.kernel.org \
/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.