All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: azurIt <azurit@pobox.sk>
Cc: "linux-raid@vger.kernel.org List" <linux-raid@vger.kernel.org>
Subject: Re: RAID0 size over 2 TB
Date: Mon, 8 Sep 2014 12:19:24 -0600	[thread overview]
Message-ID: <EC31326C-A2AE-4096-8542-E8E9BD5A43B7@colorremedies.com> (raw)
In-Reply-To: <20140908092450.8E735FB7@pobox.sk>


On Sep 8, 2014, at 1:24 AM, azurIt <azurit@pobox.sk> wrote:

>> 
>> CC: linux-raid@vger.kernel.org
>> On Mon, 8 Sep 2014, azurIt wrote:
>> 
>>> 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.
>>> 
>>> # cat /proc/partitions
>>> major minor  #blocks  name
>>> 
>>>  8       33 2147483647 sdc1
>>>  8       49 2147483647 sdd1
>> 
>> .... they're not.
>> 
>> -- 
>> Mikael Abrahamsson    email: swmike@swm.pp.se
> 
> 
> 
> 
> so why cgdisk and also fdisk sees them as 4TB?

Newer versions of fdisk do support GPT. Yours isn't new enough. Since you have cgdisk, you should use:

gdisk -l /dev/sdc

or

parted -s /dev/sdc u s p


Chris Murphy

  reply	other threads:[~2014-09-08 18:19 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 [this message]
2014-09-08  7:28     ` NeilBrown
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=EC31326C-A2AE-4096-8542-E8E9BD5A43B7@colorremedies.com \
    --to=lists@colorremedies.com \
    --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 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.