If you’re like me and installed Fedora in a VirtualBox by just clicking through defaults you’ll find that when you try to do anything you’ve setup a box with very little disk space. At least in my case I ended up with a virtual hard drive with 8G max and a root partition with 5.5G allocated. It’s okay though because by blindly clicking through defaults I ended up using LVM2 for that root partition.

So since I have LVM in place I can simply add another disk and extend the logical volume/partition onto it. Easy as cake as they say.

1) Add a disk – this is VirtualBox so shut down the the box and then from settings, storage add another device. I went with 50G this time. Really – you bought developers PCs with only 138G drives in them? Oh well, it’ll expand to use what I need up to that 50G limit.

2) Add an LVM physical volume – startup that machine and then use “fdisk /dev/sdb” to create a partition on the new drive and then “pvcreate /dev/sdb1″

3) Add that physical volume to my volume group. I didn’t know the name of that volume group so “vgs” showed me that it is vg_machinename and then “vgextend vg_machinename /dev/sdb1″

4) Extend the logical volume to increase take advantage of some of that newly available space. I wasn’t sure of the logical volume name so “df” showed me that it is /dev/mapper/vg_machinename-lv_root and so “lvextend -L50G /dev/mapper/vg_machinename-lv_root” and I’m good right? Well sort of. The logical volume is bigger but the filesystem is still the same size.

5) Extend the file system over that new larger logical volume. Since it’s mounted on / I can’t unmount so shutdown and boot off of the live CD image I used to install. Then “e2fsck -f /dev/mapper/vg_machinename-lv_root” followed by “resize2fs /dev/mapper/vg_machinename-lv_root”.

6) Unmount the CD image, reboot and voila – lots more elbow room.

Not exactly an end user kind of operation but not a horrible ordeal either and all without losing the stuff I had on there already. The same basic process should work for other distributions as long as you’re using LVM2 and ext4 as the filesystem though the naming will likely be somewhat different.

Mar 132011

I seem to always run into problems when attempting to update my iPhone software through iTunes. I’d get through downloading the file and then when iTunes starts to process the download it would give an error about network connection timed out. It’s kind of a curious error because as far as I could tell it had already download the update. I had a hunch that what iTunes is doing at that point is making another network query to validate the install and that connection was for some reason being blocked by my firewall which is Kaspersky. So I proceeded to shutdown everything but iTunes and went into Kaspersky to pause my protection and voila – the update downloads and proceeds just fine. Once it got to the point where it was actually updating the software on the iPhone I re-enabled Kaspersky and the update went through without a hitch.

I actually seem to remember having this same exact problem on the prior iOS update and not that I think about it, it seems that I had to disable the firewall to get that one through as well.

In general I’m pretty happy with Kaspersky but like just about all Windows anti-virus/firewall software I’ve tried the false negatives are a bit annoying. And I really wish it would offer more insight into exactly what it was doing.

© 2011 nestoriak.com Suffusion theme by Sayontan Sinha