From: Herta Van den Eynde <herta.vandeneynde@cc.kuleuven.be>
To: Tyler <pml@dtbb.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm create size problem
Date: Wed, 04 May 2005 12:42:58 +0200 [thread overview]
Message-ID: <4278A732.10105@cc.kuleuven.be> (raw)
In-Reply-To: <4278A2D2.1020901@dtbb.net>
I was trying mdadm-1.11.0 which I picked up from
http://www.be.kernel.org/pub/linux/utils/raid/mdadm/mdadm-1.11.0.tar.gz
on Red Hat Advanced Server 2.1 most recent kernel update:
# cat /proc/version
Linux version 2.4.9-e.62enterprise (bhcompile@tweety.build.redhat.com)
(gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-129.7.2)) #1 SMP Fri
Apr 8 18:46:17 EDT 2005
Kind regards,
Herta
Tyler wrote:
> What version were you trying? 1.9.0 and 1.11.0 are considered the
> latest stable versions i believe.
>
> Regards,
> Tyler.
>
> Herta Van den Eynde wrote:
>
>> FWIIW, I reverted to mdadm-1.4.0-1, and that version creates the
>> RAID1+0 just fine.
>>
>> Herta
>>
>> Herta Van den Eynde wrote:
>>
>>> OK, there's definitely something wrong here. I ran a
>>> # mdadm --zero-superblock --force /dev/sdX
>>> followed by
>>> # dd if=/dev/zero of=/dev/sdX bs=64k
>>> where X=[g-in-p], and when I try to create a RAID 1 using two of these
>>> devices, it still sets the size to 139904K. When I create a RAID 0
>>> using the same devices, mdadm does set the size correctly.
>>>
>>> # mdadm --create --verbose /dev/md6 --level=1 --raid-devices=2 /dev/sdh
>>> /dev/sdo
>>> mdadm: size set to 139904K
>>> mdadm: array /dev/md6 started.
>>>
>>> # mdadm --create --verbose /dev/md6 --level=0 --raid-devices=2 /dev/sdh
>>> /dev/sdo
>>> mdadm: chunk size defaults to 64K
>>> mdadm: array /dev/md6 started.
>>> # mke2fs -j -v /dev/md6
>>> (...)
>>> # mount /dev/md6 /mnt; df /mnt
>>> Filesystem 1k-blocks Used Available Use% Mounted on
>>> /dev/md6 141124600 32828 133923052 1% /mnt
>>>
>>> Is this a bug, or am I overlooking something?
>>>
>>> Herta
>>>
>>>
>>> Herta Van den Eynde wrote:
>>>
>>>> Red Hat AS 2.1 mdadm 1.11
>>>> I have two devices that used to be part of a now corrupt RAID10
>>>> configuration. When I try to reuse them to create a RAID1, it only
>>>> uses about 1 third of the diskspace available.
>>>> # fdisk -l /dev/sdg
>>>>
>>>> Disk /dev/sdg: 255 heads, 63 sectors, 8924 cylinders
>>>> Units = cylinders of 16065 * 512 bytes
>>>>
>>>> Device Boot Start End Blocks Id System
>>>> /dev/sdg1 1 8924 71681998+ fd Linux raid autodetect
>>>>
>>>> # fdisk -l /dev/sdn
>>>>
>>>> Disk /dev/sdn: 255 heads, 63 sectors, 8924 cylinders
>>>> Units = cylinders of 16065 * 512 bytes
>>>>
>>>> Device Boot Start End Blocks Id System
>>>> /dev/sdn1 1 8924 71681998+ fd Linux raid autodetect
>>>>
>>>> # mdadm --create --verbose /dev/md5 --level=1 --raid-devices=2
>>>> /dev/sdg /dev/sdn
>>>> mdadm: /dev/sdg appears to contain an ext2fs file system
>>>> size=419520K mtime=Mon May 2 17:04:04 2005
>>>> mdadm: /dev/sdn appears to contain an ext2fs file system
>>>> size=419520K mtime=Mon May 2 17:04:04 2005
>>>> mdadm: size set to 139904K
>>>> Continue creating array? n
>>>>
>>>> If I try to add the --size option, even a size that is 139904K or
>>>> less, it tells me the size is invalid:
>>>>
>>>> # mdadm --create --verbose /dev/md5 --level=1 --raid-devices=2
>>>> /dev/sdg /dev/sdn --size=139904K
>>>> mdadm: invalid size: 139904K
>>>>
>>>> I did reboot the system after fdisk'ing the devices.
>>>>
>>>> Do I need to low-level format these devices to be able to reuse them?
>>>>
>>>> Kind regards,
>>>>
>>>> Herta
>>>
>>>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Herta Van den Eynde -=- Toledo system management
K.U. Leuven - Ludit -=- phone: +32 (0)16 322 166
-=- 50°51'27" N 004°40'39" E
"I wish I were two little cats. Then I could play together."
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-05-04 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 13:53 mdadm create size problem Herta Van den Eynde
2005-05-04 9:51 ` Herta Van den Eynde
2005-05-04 10:12 ` Herta Van den Eynde
2005-05-04 10:24 ` Tyler
2005-05-04 10:42 ` Herta Van den Eynde [this message]
2005-05-23 23:43 ` Neil Brown
2005-05-24 7:26 ` Luca Berra
2005-05-24 10:51 ` Neil Brown
2005-05-24 11:34 ` Luca Berra
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=4278A732.10105@cc.kuleuven.be \
--to=herta.vandeneynde@cc.kuleuven.be \
--cc=linux-raid@vger.kernel.org \
--cc=pml@dtbb.net \
/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).