Tag Info

Hot answers tagged

21

This is an interesting question... I don't think there's a definitive answer, but I can give some historical context on how best practices surrounding this may have changed over time. I've had to support thousands of Linux VMs deployed in various forms across VMware environments since 2007. My approach to deployment has evolved, and I've had the unique ...


7

You're right in many ways, I can see the argument - there is one issue that could prove tricky though. If you use Resource Pools (and I know I don't, hateful things) then VMs can get more IO time if they have more disks - in extreme resource constrained situations a VM with two disks could get twice as much IO resources as one with a single disk. This may ...


4

When I worked in infrastructure at a particular "large virtualization software company," we often needed to increase the size of a vm's filesystem. We used ext3/4 at the time. Increasing the virtual disk is very easy, picking up the new device size in a live OS is relatively easy (poke around in /sys), resizing the ext3/4 filesystem live was easy, but what ...


4

The main problem, that the bootloaders are a little bit complex today, and practically they need to be booted as well. Even this "bootloader booting code" is too big for the around 300 byte of code in the MBR (master boot record). This is because the boot loaders are using normally an extra data area, around 10-30 kbyte, after the master boot record. On ...


3

When you say "EFI-only partition table" I suspect you're talking about a GUID Partition Table (GPT). Per Microsoft, Windows 7 and Windows Server 2008 can boot from a GPT, provided you're running an x64 build in a system with UEFI firmware.


3

Did you expand the storage at any point? It looks like the file system wasn't resized when the underlying storage was increased. For ext3/ext4 you would use resize2fs to grow the file system. For XFS you would use grow_xfs. More information.


2

Yes, and no. Yes, it is possible to scatter your files for sure: fill your file system enough (almost full). No, it's not trivially possible to influence the actual physical distribution of your files to make sure the blocks of a particular file get placed to a certain part of the backing device. By using fallocate to preallocate disk space to files, ...


1

Yes, XFS doesn't shrink. Yes, there is no mandatory requirement to have /home as a separate file-system (although a number of reasons to do so are listed here) Back-up the contents of /home, unmount the home directory and discard the logical volume with lvremove and the blocks you had assigned will be returned to the volume group as free space, which can ...


1

While your question as written is about VMWare (ESXi), I'd like to add a situation where I switched back to using partition tables after having the same idea on KVM. It turned out that if you have LVM volumes as disks for VMs and create an LVM volume group inside the VM without using partitions (using the whole virtual disk as PV), this VG will be visible ...



Only top voted, non community-wiki answers of a minimum length are eligible