Local time and alternate temp directory for capture option

[Fog_Newb]

Hi,
It would be cool to have an option that shows image capture and deployment using local time of the FOG server (not UTC). Another would be an option to specify a alternate temp directory for FOG to when capturing images. This would help keep VM drives from blowing up in size.

Thank you

[AUTH IT Center]

Hello,

for the second part you can mount anything (e.x. /sdb, /storageip, /nasdrive ) in /images and keep the storage independent from the VMs primary disk.

[Fog_Newb]

@AUTH-IT-Center

Thanks. I currently have a 2nd drive mounted as /images. That’s is the one that keeps blowing up. I thought about mounting a separate drive as /images/dev (that’s were FOG seems to create the temp files). I may do that and see how it goes.

[AUTH IT Center]

@Fog_Newb

99% it will work. The path /images/dev is the tmp location for image creation, so if you mount a 3rd drive you can achieve the expected result.

[Fog_Newb]

@AUTH-IT-Center Something weird happened after mounting another drive as /images/dev I made sure to copy everything from the original /images/dev and copy them to the new mounted /images/dev

Then

sudo chown -R fogproject /images

sudo chown -R fogproject /images/dev

After doing this and capturing an image. The tmp image remained in /images/dev and the usual directory where that image was stored, was no longer seen as directory. But it wasn’t a symbolic link either. This only happened after trying to capture the images using the new mount.

Just to make sure it wasn’t something I did when mounting the new /images/dev storage drive, I made sure the directories for the remaining pre-existing captured images were still being seen as directories. They were. I then captured one of those those images and just like that, the directory for that image was no longer seen as a directory and the tmp image for that capture remained in the /images/dev. Weird.

[AUTH IT Center]

@Fog_Newb

as described in https://www.reddit.com/r/linux4noobs/comments/119i2vy/is_it_possible_to_mount_one_drive_as_a_subfolder/

probably its best to move everything away from the mount points and then create the new structure. Also as always in this occasions BACKUP before testing.

[Fog_Newb]

@AUTH-IT-Center

Yes, the reddit post is the way the drives were mounted. Just to make sure it wasn’t user error, I spun up another FOG VM really quick and during the installation specified the mount points

Same thing

It’s looking like FOG has issues if the temp storage location is on a different volume than the images.

[Tom Elliott]

@Fog_Newb did you make sure the /images/dev is owned by fogproject:fogproject user and that there’s the ever useful (needed) .mntcheck file?

[Fog_Newb]

@Tom-Elliott

Yes, I even spun up a new FOG VM where the mount points were created before FOG was installed to makesure the FOG installer created all the files and set permissions.

edited - words