Systems Management

When you export an image, it is written as a pkg file into the \\k2\restore share. This ironically can take up more space as the image will exist in the imagestore ( image list ) and as a package file in the restore share. So you would first want to copy the exported PKG and XML files off the restore share to some remote storage and then delete them from the restore share. Once that is complete you can delete the image from the system image list.

How much space you get back depends a lot on what type of image you deleted. If you deleted a WIM image ( Native to the K2000 not created with KNIT ) you will free up the exact space the image showed as being used on the image list page.   If your image was created with KNIT you will have to back up and delete the WIM image from the \\k2\\petemp\ImageStore\WIMNAME manually to go along with your exported image pkg file. If the Image was a Kimage,  (and you have more than one Kimage of the same architecture ) you may free up very little space. This is because Kimages use data deduplication so only one copy of a file is stored on the K2000 no matter how many Kimages (of that OS type ) you have. As an example the first Windows 7 x64 kimage you capture will take up the exact amount of space shown on the image list page. The second windows 7 x64 kimage you take will use space for only the files it contains that are different from the first image, though it will show the full size needed for deployment on the image list page.  If you choose to delete the first or second image, you will only be deleting the files contained in the image you are deleting that are not part of the image you have not deleted so the space returned will be much less than you might expect.

Once you have deleted a Kimage, its a good idea to run a file purge  (Settings & Maintenance > Appliance Maintenance >  Purge unused system image files). This essentially runs an audit on all files stored on the K2000 and deletes any file not associated with a current image. On 3.6 or better the purge runs each night automatically, on earlier versions it must be run manually. Depending on how long its been since the last purge ( a maximum of 24 hours for 3.6 ) and the number of images deleted it may take a couple hours to complete.

Also note the disk usage pie chart takes 15 minutes to update so if you delete a wim image and its not reflected in the disk utilization chart wait 15 -20 minutes and check it again.   

As to your second question, if the free disk space gets too small, certain functions may fail. You may find you can not run an export, download a USB image, import a new pkg, etc. If the free space goes to zero you will find logging stops and you will not be able to deploy images accurately and certainly wont have any logs of the deployment. It is best practice to keep 20GB of free space at all times to allow for functions (like exports) that need working space.