Yousuf Khan wrote:
> I've recently upgraded to an SSD as my boot drive, so my old 1TB boot
> drive's system partition is no longer needed. I had that old drive
> separated into an NTFS system partition of about 200GB and an NTFS data
> partition of about 700GB, as well as less than 100GB of Linux
> partitions. I was thinking of adding that 200GB space back to the 700GB
> data partition. When I went into Disk Management, it said that it wanted
> to convert the partitions into dynamic partitions from basic partitions.
> I'm just a little concerned that if it converts it to dynamic, I'll lose
> the existing data on the 700GB partition, or the sub-100GB Linux
> partitions.
>
> The 200GB physically comes before the 700GB partition on that disk. So I
> assume the reason it's going convert to dynamic is because it wants to
> logically add the earlier partition to the end of the later partition.
> Also the 200GB is on a primary partition, while the 700GB is on an
> extended partition. Do I have to worry about losing any of the existing
> data?
>
> Yousuf Khan
I expect you'll have fixed this, before the answer comes back :-)
http://en.wikipedia.org/wiki/Logical_Disk_Manager
"Dynamic disks support multipartition volumes"
That suggests to me, that two physical chunks of space can be
"spanned" to form a volume.
*******
Physical (the end of the volume is now "ahead" of the beginning)
<- 200GB -> <-- 700GB -->
Volume (right after spanning stage)
<-------- 700 + 200 -------->
Structure right before expansion
<----------- 900 -----------> (total space)
<----- 700 -----> unalloc (what the file system thinks just after span, but before expand)
<----------- 900 -----------> (what the file system thinks, after "expanding to fill space")
Making the change consists of two stages. The first stage, is adding
sectors to the volume. At this point, the file system has not taken
advantage of the additional space. The second stage, is expanding
file system structures and moving the defined end of the file system,
as close as possible to the physical end. If the number of clusters
doesn't round off nicely, there could be a fraction of something left
unoccupied at the very end.
I expect the thing is tolerant of the end being ahead of the
beginning. But my approach to disk layouts, is to make them
as easy to understand as possible, both for me later, and for
any repair/recovery tools I may choose to use in the future.
Even if it means the manipulation takes a bit more time.
The way I'd probably do it, is use a second disk, move the 700GB
to the beginning of the second disk, expand it by 200GB more, then
copy over the Linux partition. Then, "dd" the thing back. That's assuming
the tool you use for it, doesn't screw up the GUID on the Linux, or the
VolumeID on the Windows partitions, in which case I might have some repair
work to do. (I hate the Linux GUID concept. Just a PITA.)
Paul