Bug 762512 (GLUSTER-780) - GPT corruption occurs
Summary: GPT corruption occurs
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-780
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: 3.2
Assignee: Timothy Asir
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-27 00:25 UTC by Balamurugan Arumugam
Modified: 2011-02-10 12:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Balamurugan Arumugam 2010-03-27 00:25:53 UTC
dmesg:

kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
GPT:Primary header thinks Alt. header is not at the end of the disk.
GPT:1564344321 != 2147483646
GPT:Alternate GPT header not at the end of the disk.
GPT:1564344321 != 2147483646
GPT: Use GNU Parted to correct GPT errors.
 sdd1
sd 2:0:0:2: [sdd] Attached SCSI disk


/proc/partitions:

major minor  #blocks  name

   8        0   35155968 sda
   8        1    3906233 sda1
   8        2   31249701 sda2
   8       16 1073741823 sdb
   8       17 1073741790 sdb1
   8       32 1073741823 sdc
   8       33 1073741790 sdc1
   8       48 1073741823 sdd
   8       49  782172127 sdd1
   8       64 1073741823 sde
   8       80 1073741823 sdf
   8       96  490602498 sdg


Model: AMCC 9690SA-4I DISK (scsi)
Disk /dev/sdd: 1100GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End    Size   File system  Name     Flags  
 1      17.4kB  801GB  801GB  ext3         primary  msftres



It suppose to be full size (1100GB)

Comment 1 Balamurugan Arumugam 2010-12-17 07:08:52 UTC
This problem occurs due to on-the-fly disk expansion from 801GB to 1100GB in hardware RAID level.  There is no support in linux (v2.6.30) to do on-the-fly disk expansion on mounted file system.


Note You need to log in before you can comment on or make changes to this bug.