1 (edited by tsf0x13 2012-12-11 07:27:20)

Topic: problem with resize partition [SOLVED]

After resizing the partition with GParted 0.6.0 appeared unallocated space.
After that, I booted from Live-CD (0.14-1, latest version) and tried to check partition, as I suggested gparted.
Now i have 25 Tb volume with 1.8 Tb unallocated space on it. I can't fix it sad
Anyone can help me?



fdisk -l -u

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

Disk /dev/sdb: 27960.2 GB, 27960226611200 bytes
255 heads, 63 sectors/track, 3399303 cylinders, total 54609817600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe907e907

parted /dev/sda unit s print

Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1  4294967295  2147483647+  ee  GPT
[root@tht13 tsf]# parted /dev/sdb unit s print
Model: Adaptec vol1 (scsi)
Disk /dev/sdb: 54609817600s
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start  End           Size          File system  Name  Flags
1      34s    54609815551s  54609815518s  xfs

2

Re: problem with resize partition [SOLVED]

http://i52.fastpic.ru/big/2012/1210/7d/e0bd6299cc90a2b8bf982ac64efda07d.jpeg

3

Re: problem with resize partition [SOLVED]

http://i54.fastpic.ru/big/2012/1210/59/03d5de9673d512edce139110d6265359.jpeg

4

Re: problem with resize partition [SOLVED]

GParted 0.14.0

Libparted 2.3

Check and repair file system (xfs) on /dev/sda1  01:49:22    ( ERROR )
       
calibrate /dev/sda1  00:00:01    ( SUCCESS )
       
path: /dev/sda1
start: 34
end: 54,609,815,551
size: 54,609,815,518 (25.43 TiB)
check file system on /dev/sda1 for errors and (if possible) fix them  01:49:21    ( SUCCESS )
       
xfs_repair -v /dev/sda1
       
Phase 1 - find and verify superblock...
Not enough RAM available for repair to enable prefetching.
This will be _slow_.
You need at least 3840MB RAM to run with prefetching enabled.
- block cache size set to 512 entries
Phase 2 - using internal log
- zero log...
zero_log: head block 10 tail block 10
- scan filesystem freespace and inode maps...
- found root inode chunk
Phase 3 - for each AG...
- scan and clear agi unlinked lists...
- process known inodes and perform inode discovery...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- process newly discovered inodes...
Phase 4 - check for duplicate blocks...
- setting up duplicate extent list...
- check for inodes claiming duplicate blocks...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
Phase 5 - rebuild AG headers and trees...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- reset superblock...
Phase 6 - check inode connectivity...
- resetting contents of realtime bitmap and summary inodes
- traversing filesystem ...
- agno = 0
- agno = 1
- agno = 2
- agno = 3
- agno = 4
- agno = 5
- agno = 6
- agno = 7
- agno = 8
- agno = 9
- agno = 10
- agno = 11
- agno = 12
- agno = 13
- agno = 14
- agno = 15
- agno = 16
- agno = 17
- agno = 18
- agno = 19
- agno = 20
- agno = 21
- agno = 22
- agno = 23
- traversal finished ...
- moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...

XFS_REPAIR Summary Sun Dec 9 21:13:10 2012

Phase     Start     End     Duration
Phase 1:    12/09 19:23:50    12/09 19:23:51    1 second
Phase 2:    12/09 19:23:51    12/09 19:24:05    14 seconds
Phase 3:    12/09 19:24:05    12/09 20:17:53    53 minutes, 48 seconds
Phase 4:    12/09 20:17:53    12/09 21:12:30    54 minutes, 37 seconds
Phase 5:    12/09 21:12:30    12/09 21:12:35    5 seconds
Phase 6:    12/09 21:12:35    12/09 21:13:10    35 seconds
Phase 7:    12/09 21:13:10    12/09 21:13:10   

Total run time: 1 hour, 49 minutes, 20 seconds
done
grow file system to fill the partition  00:00:00    ( ERROR )
       
mkdir -v /tmp/gparted-mM5JE4  00:00:00    ( SUCCESS )
       
Created directory /tmp/gparted-mM5JE4
mount -v -t xfs /dev/sda1 /tmp/gparted-mM5JE4  00:00:00    ( ERROR )
       
mount: File too large
rmdir -v /tmp/gparted-mM5JE4  00:00:00    ( SUCCESS )
       
Removed directory /tmp/gparted-mM5JE4
libparted messages    ( INFO )
       
The backup GPT table is corrupt, but the primary appears OK, so that will be used.

5

Re: problem with resize partition [SOLVED]

There appears to be a problem with the GUID partition table.  To fix this you might try using parted on the disk device and answering "yes" if it prompts you to fix the partition table.   To try this use the following command (as root):

parted /dev/sda unit s print

It appears that GParted was unable to mount the XFS partition, and hence could not issue the grow command.

You might try manually mounting the partition and then growing the file system with the following commands (as root):

mkdir /mnt/mymnt

mount -v -t xfs /dev/sda1 /mnt/mymnt

xfs_grow_fs /mnt/mymnt

umount -v /mnt/mymnt

6

Re: problem with resize partition [SOLVED]

Solved! Thanks a lot!

7

Re: problem with resize partition [SOLVED]

'Glad that you were able to resolve the problem.  :-)

And thank you for editing the initial post to prefix SOLVED in front of the title.  This can help other users searching for answers to similar questions.