df vs diskutil, resize gone wrong
df vs diskutil, resize gone wrong
- Subject: df vs diskutil, resize gone wrong
- From: Chris Murphy <email@hidden>
- Date: Sun, 15 Apr 2012 17:59:36 -0600
User on 10.7.x used Boot Camp Assistant to Remove Windows 7. The user reports the process completed without error.
'diskutil resizevolume <dev> limits' reports a current size of 800GB. 'disk util' info reports a Total Size of 800GB. However Disk Utility, and 'df -h' report the HFS volume as 465G total, 260G used, 204G free.
The GPT reports:
gpt show: /dev/disk0: GPT partition: type=48465300-0000-11AA-AA11-00306543ECAC, start=409640, size=1562499968
And there is a stale hybrid MBR still in place:
gpt show: /dev/disk0: MBR part: type=175, start=409640, size=974609344
It reports 465G.
So diskutil list and resizevolume, and df consistently using only the GPT? Or sometimes the MBR? Or are they looking at the file system itself?
I would like to think that 'diskutil resizevolume limits' would inquire with both GPT and the filesystem. But one of these is wrong, as if the process was interrupted. I've told the user to repartition the disk and start from scratch, they have backups. I'm fairly adept at the partitioning angle, but since the GPT and MBR disagree on rather fundamental sizing, and I'm unfamiliar with how to ask the file system how big it thinks it is, I don't have a way to resolve the ambiguity.
Kindof an interesting problem though.
Chris Murphy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden