![]() Need administrator privileges for running auto update on Zimbra Desktop(Windows 7, Windows 10) Installation of ZD in silent mode fails on windows OS (Java not found error)ĭate format for “Sync messages to fixed date” on add new account page is incorrect and causes problem Zimbra Desktop 7.3.0 includes a long list of fixed issues which you can find here. Windows: Make Zimbra Desktop default email application (mailto protocol) Spell check while composing new email not working in 7.3 ![]() New auto-update framework for Windows and Mac OS X dev/sda5 501760 125827071 62662656 8e Linux LVMĭisk /dev/mapper/mta–2-root: 63.Replace Prism framework with Nw.js for all platforms I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I am trying to extend logical volume from 60 Gigs to 75 Gigs, I increased size of the (virtual) drive from VMware, and I can see fdisk -l is showing new size now, but I am not seeing new size or Free space when running pvdisplay. We can do that while the volume is in use by running this command:Īfter that has completed we are finished! If you want to double check that all is well you can run df -h to verify the size of the logical volume mounted at /opt/zimbra. Lvresize -L +38GB /dev/mapper/data_vg-zimbraįinally the last step now that our new 38GB has been allocated to the data_vg volume group is to expand our ext3 file system. Next we need to move that 38GB’s of free space into allocated space to our data_vg volume group. If all is well you should see 12GB in use and 38GB free. Step 2 is verify that the Volume Group sees the additional space, to check this run the following command: The first step is to expand our physical volume, to do that we need to run this command:Īfter running this command we can run “pvdisplay” and we will see the statistics about out physical volume /dev/sdb, and it will tell us that it is now seen as 50GB and that there are “Free PE”, see the screenshot blow. We should see 50GB on the right, and not 12GB.Īfter verifying that the volume is showing the larger size in the partition editor we can start the process, just make sure to exit cfdisk without changing anything. Once you’re on the CLI we can start to do what we need to make the expansion happen, first lets start by making sure that Ubuntu sees the larger drive to do that we can type “cfdisk /dev/sdb”. The best part is that we can do it all while the server (and volume) is online and working! Steps to Expansion So in LVM terms, we are going to grow our Physical Volume, then we will add that new space to our Logical Volume, and finally we will tell the EXT3 file system that it has just grew by 38GB for a total of 50GB. ![]() This is the “device” that is formatted with a file system, and the part that is mounted. Logical Volume: A Logical Volume is a bucket, or area of space from a volume group that is used in the linux operating system much like a traditional disk or partition is. ![]() Volume Group: A Volume Group is a group of Physical Volumes that are grouped together to provide a pool of space. Physical Volume: A Physical Volume is a partition or block device that will actually hold the 1’s and 0’s that you plan to write. There are several terms that we will be mentioning in the article, they are: Physical Volume, Volume Group, Logical Volume. LVM stands for logical volume manager, and it is a more dynamic way to manage storage on a linux system than the traditional partition managers. Overview of LVMīefore I get into the nuts and bolts of what to type to get things expanded I thought I would first talk a little about how LVM works, as it might help you understand some of the steps and why we need to do what we are going to do. Then we need to login to the Zimbra CLI, to do this use root as the username and vmware as the password, unless you changed it during the Zimbra setup. Basically what we need to do is go into the properties and find “Hard Disk 2”, then we raise it from 12GB to whatever size we want, I picked 50GB. We know that the appliance runs on Ubuntu 10.04 LTS and that its using LVM for volume management. This would probably be more then enough for lab purposes but I decided that I needed to expand it to 50GB, which is probably a much more reasonable size for an SMB. One of the first things I noticed was that by default the appliance version only ships with a 12GB VMDK for the message store. Lately I’ve been testing out the new Zimbra 8 Beta appliance in both my lab as well as on the cluster where I host my blog and some other sites.
0 Comments
Leave a Reply. |