Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've created a 10TB LUN (7x 2TB disks in RAID6) on a storage array and presented it to our backup server, running Ubuntu 10.04 32-bit. The OS only sees 8000GB as per fdisk:

# fdisk -l /dev/sde

WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk
doesn't support GPT. Use GNU Parted.


Disk /dev/sde: 8000.0 GB, 7999999442944 bytes
255 heads, 63 sectors/track, 972611 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sde doesn't contain a valid partition table

This isn't a filesystem issue (I plan to use XFS FWIW), because I'm seeing the incorrect capacity before I've even partitioned this device.

I've searched Google high and low and I can't seem to find an answer on where this limit is. Is it because of the 32-bit kernel?

update: using parted doesn't make a difference.

# parted /dev/sde
GNU Parted 2.2
Using /dev/sde
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel gpt
(parted) print
Model: YA-16SAE Backup_Vol_001 (scsi)
Disk /dev/sde: 8000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start  End  Size  File system  Name  Flags

(parted) quit                                                             
Information: You may need to update /etc/fstab.
share|improve this question
1  
Did you even try the suggestion fdisk gave you? Use parted to see more accurate information. –  Janne Pikkarainen Jul 19 '12 at 8:04
    
@JannePikkarainen: no difference, updated question. –  ThatGraemeGuy Jul 19 '12 at 8:13
    
At this point the question becomes, did you configure the storage array correctly? That's what I would be checking right now. –  Michael Hampton Jul 19 '12 at 8:22
    
@MichaelHampton: the configurable values when creating the LUN are the stripe size (which AFAIK has no impact on this) and ">2TB volume support" which is either "64bit LBA" (which I selected) or "4k block". I don't recall the specifics, but last time I looked at this, "64bit LBA" was preferred over "4k block". –  ThatGraemeGuy Jul 19 '12 at 8:41
    
What does dmesg say on the matter? Can you access the LUN with the full 10TB from a different type of system? –  womble Jul 19 '12 at 11:46
add comment

2 Answers

First, you shouldn't be using fdisk. It can't create partitions over 2TB anyway.

Check to see whether it's a problem with fdisk by using parted:

parted /dev/sde print

If things look good, put a GPT label and a partition on it:

parted /dev/sde mklabel gpt
parted /dev/sde mkpart primary xfs 1 -1

If things don't look good (which you said they didn't) then it's time to double check that you actually put all seven disks in the array, rather than just six of them.

share|improve this answer
    
I wasn't using fdisk to create partitions, I just used the -l option to view the block device properties. parted also only sees it as 8000GB. –  ThatGraemeGuy Jul 19 '12 at 8:22
add comment

Well that's annoying. After a reboot its now showing as 10000GB. Partitioned, formatted, mounted, rebooted, no issues.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.