CentOS lists /dev/sda1 and /dev/mapper/centos-root, which is a link to /dev/dm-0, while GParted lists /dev/sda1 and /dev/sda2. There seems to be a discrepancy between the devices my guest OS reports and what partitions GParted reports. The first time I tried to fill up the space, when I restarted the VM after filling it up, the VHD file on my host did increase by about 1GB, however it won't expand any more now. However when I fill up all of this space on the guest OS (by writing a long seq into a file), the drive not does automatically expand. The actual size of the VHD right now is still 14.4GB. So VirtualBox recognizes that the VHD can go up to 100GB and sda2 takes up most of that space. Then I used GParted to expand the sda2 partition so that it took up the extra space. While working on a project I realized that I would need much more space, so I used VBoxManage to increase the maximum to 100GB. mpack Site Moderator Posts: 37092 Joined: 4.I'm working on a 64-bit CentOS 7 VM on my Windows 10 host, and I have a dynamically-allocated VHD that is giving me problems.Īt first, the VHD's maximum size was set to 16GB, functionally about 14.4 usable. In fact my current PC has a 512GB SSD plus a 2TB HDD: it so happens that it uses EFI and therefore defaulted to GPT, but it could still be using MBR no problem. So MBR managed to stay relevant (albeit with a mild tweak halfway to add LBA addressing) for 3 decades and during an incredible several orders of magnitude size increase, so I'd say that the designer of MBR did a damn good job. Hard drives were typically 10MB or 20MB at that time, so a 2TB drive is 100,000 times the size of one of those. MBR (which includes the legacy partition map) was designed in the DOS era, sometime around DOS 2.11 as I seem to recall, when the first hard drives were installed in PCs. Of course text is readibly compressed (unlike JPEGs which are already compressed), so 2TB can store a huge amount of mixed text and graphics. Quick calculation: if the average size of the JPEG is 128KB, then a 2TB drive can store 17,179,869 of them.
0 kommentar(er)
