I would like to clarify the right way to deploy MapR on the largest disks.

Having installed a new 3TB Seagate Barracuda disk (STBD3000100) I found that both "fdisk -l" and MapR Control System can only recognize the first 2.2TB, consistent with DOS partition table limitation:

[root@hostname ~]# fdisk -l  
Disk /dev/sdb: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sdb doesn't contain a valid partition table
[root@hostname ~]#

Seagate documentation directs me to their "beyond 2TB" support site that says that larger disks are automatically recognized by Linux kernels "v2.6.35 or newer" which excludes CentOS 5.x

I could see a possible solution being to format the disk as GPT using Parted and if it succeeds at creating a 3TB GPT partition (/dev/sdb1) then install MapR FS there. I have done this kind of formatting on another box (non-MapR) and here is how fdisk sees that format:

[root@hostname ~]# fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.

Note: sector size is 4096 (not 512)

WARNING: The size of this disk is 3.0 TB (3000592977920 bytes).
DOS partition table format can not be used on drives for volumes
larger than 2.2 TB (2199023255040 bytes). Use parted(1) and GUID
partition table format (GPT).

Disk /dev/sdd: 3000.5 GB, 3000592977920 bytes
255 heads, 63 sectors/track, 45600 cylinders
Units = cylinders of 16065 * 4096 = 65802240 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1       45601  2930266576   ee  EFI GPT
[root@hostname ~]#

My question is whether installing MapR-FS on large-sized GPT partitions is supported / tested and if not what is the alternative solution. The reason I am even asking is because MapR Control System only sees the disk (/dev/sdb) as 2TB...

asked 24 Mar '12, 14:43

tc_dev's gravatar image

accept rate: 40%

The MapR formatting tool just uses whatever pathname you provide (whether it be a real disk, a flat file, or an LVM generated paritition). So if /dev/sdd1 is provided, the formatting should work.

The MapR Control System uses hdparm to figure out various things about the drive, and hdparm may have the same limitation as fdisk. But the formatting stuff doesn't do anything further than opening the provided pathname and using "stat" to read the size of the disk. Give it a try and let us know if it works for you.


answered 24 Mar '12, 18:40

MC%20Srivas's gravatar image

MC Srivas ♦♦
accept rate: 32%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 24 Mar '12, 14:43

Seen: 3,061 times

Last updated: 31 Oct '12, 05:40

powered by OSQA