From: NeilBrown <neilb@suse.de>
To: azurIt <azurit@pobox.sk>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0 size over 2 TB
Date: Mon, 8 Sep 2014 17:28:32 +1000 [thread overview]
Message-ID: <20140908172832.7543b241@notabene.brown> (raw)
In-Reply-To: <20140908091811.1DD1140C@pobox.sk>
[-- Attachment #1: Type: text/plain, Size: 2813 bytes --]
On Mon, 08 Sep 2014 09:18:11 +0200 "azurIt" <azurit@pobox.sk> wrote:
> >
> > CC: linux-raid@vger.kernel.org
> >On Sat, 06 Sep 2014 23:09:28 +0200 "azurIt" <azurit@pobox.sk> wrote:
> >
> >> Hi,
> >>
> >> i'm having problems with growing my RAID0 array over 2 TB. I installed two 4 TB drives, created 4 TB partitions but array cannot be resized over 2 TB. Superblock versoin is 0.90 and kernel version is 3.2.53 - according to linux RAID wiki, it should support 4 TB component/array size:
> >> https://raid.wiki.kernel.org/index.php/RAID_superblock_formats#The_version-0.90_Superblock_Format
> >>
> >> Some more info:
> >>
> >> # mdadm --detail /dev/md2
> >> /dev/md2:
> >> Version : 0.90
> >> Creation Time : Tue Sep 28 16:54:04 2010
> >> Raid Level : raid1
> >> Array Size : 2147483520 (2048.00 GiB 2199.02 GB)
> >> Used Dev Size : 2147483520 (2048.00 GiB 2199.02 GB)
> >> Raid Devices : 2
> >> Total Devices : 2
> >> Preferred Minor : 2
> >> Persistence : Superblock is persistent
> >>
> >> Update Time : Sat Sep 6 23:04:44 2014
> >> State : clean
> >> Active Devices : 2
> >> Working Devices : 2
> >> Failed Devices : 0
> >> Spare Devices : 0
> >>
> >> UUID : 9a363004:ad04abfe:2e31e1c3:caf66df4
> >> Events : 0.77066
> >>
> >> Number Major Minor RaidDevice State
> >> 0 8 33 0 active sync /dev/sdc1
> >> 1 8 49 1 active sync /dev/sdd1
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> # fdisk /dev/sdd
> >>
> >> WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.
> >
> >Why are you using "fdisk" even though "fdisk" is telling you not to use it?
> >
> >What does
> > cat /proc/partitions
> >
> >say about the sizes of the partitions?
> >
> >NeilBrown
> >
>
>
>
> I, of course, didn't use fdisk to create partitions - they were created using cgdisk, but it's graphical tool so i wasn't able to send output from it, so i get output from fdisk to prove, that partitions are large enough.
Yet fdisk *didn't* prove that the partitions are large enough - it said the
partitions were:
/dev/sdd1 1 4294967295 2147483647+ ee GPT
^^^^^^^^^^^
2 Gig.
And /proc/partitions tells me:
>
>
> # cat /proc/partitions
> major minor #blocks name
>
> 9 2 2147483520 md2
> 8 32 3907018584 sdc
> 8 33 2147483647 sdc1
> 8 48 3907018584 sdd
> 8 49 2147483647 sdd1
that the partitions are 2Gig. You need to sort the partition size out. I
cannot help you. I have no experience with GPT. Maybe a reboot?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2014-09-08 7:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 21:09 RAID0 size over 2 TB azurIt
2014-09-06 21:17 ` RAID0 size over 2 TB - RAID1 azurIt
2014-09-08 7:00 ` RAID0 size over 2 TB NeilBrown
2014-09-08 7:18 ` azurIt
2014-09-08 7:21 ` Mikael Abrahamsson
2014-09-08 7:24 ` azurIt
2014-09-08 18:19 ` Chris Murphy
2014-09-08 7:28 ` NeilBrown [this message]
2014-09-08 7:33 ` azurIt
2014-09-08 18:27 ` Chris Murphy
2014-09-08 19:16 ` Chris Murphy
2014-09-08 20:02 ` azurIt
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=20140908172832.7543b241@notabene.brown \
--to=neilb@suse.de \
--cc=azurit@pobox.sk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox