It does happen overnight, and the images are moved from /dev to the proper folder in /images. I was doing them all on Fridays, then I switched to another night to see if that was the issue. It worked fine at first on the other night, then the same issue popped up. I was hoping to find a log of some kind that could describe what’s happening, but failing that I’ll try to figure out a way to get a camera on one and capture an error message. The problem is that it’s intermittent; taking the same image at a different time usually works fine.
Latest posts made by Ryan Stoops
-
RE: Uploaded Image Sizes And Restores
-
RE: Uploaded Image Sizes And Restores
Looks like the partition size is actually 93.2 GB. I assume the compression is responsible for getting to ~50 GB. This is in line with most of our workstation images.
-
RE: Uploaded Image Sizes And Restores
OK, here’s some more info. This is the ls-lahRt of the corrupted image, taken 6/17:
total 11G drwxrwxrwx 2 fog fog 4.0K Jun 18 15:15 . drwxrwxrwx. 4 fog root 4.0K Jun 18 15:14 .. -rwxrwxrwx 1 fog fog 11G Jun 17 01:07 d1p3.img -rwxrwxrwx 1 fog fog 177M Jun 17 00:00 d1p2.img -rwxrwxrwx 1 fog fog 77K Jun 17 00:00 d1p1.img -rwxrwxrwx 1 fog fog 512 Jun 17 00:00 d1.mbr
Here’s the same image, taken 6/18:
total 53G drwxrwxrwx. 79 fog root 4.0K Jun 18 23:09 .. -rwxrwxrwx 1 root root 53G Jun 18 23:09 d1p3.img drwxrwxrwx 2 root root 4.0K Jun 18 22:24 . -rwxrwxrwx 1 root root 177M Jun 18 22:24 d1p2.img -rwxrwxrwx 1 root root 77K Jun 18 22:23 d1p1.img -rwxrwxrwx 1 root root 512 Jun 18 22:23 d1.mbr
So the upload process is cutting out during the upload of the third partition. Is it a permission issue?
-
Uploaded Image Sizes And Restores
Running 1.2.0 on Centos 6.6. I upload 15-25 workstation images weekly, and I’ve used this setup for over a year without any major problems. Recently, my image uploads are greatly reduced in size (from ~50GB one month to ~15GB the next on the same machine) and, after testing a restore, the machine fails to boot. I’ve looked at the web GUI imaging log, and it tells me they’ve been taking 50 mins - 1 hr each, which is pretty normal. I’ve tried adjusting the FOG_PIGZ_COMP, but it doesn’t seem to have any effect.
What’s stranger is that it’s intermittent - if I upload one day they may all be fine, but another day they seem to corrupted somehow. Is there some more detailed log where I can see what exactly is happening?
-
Disappearing Images
Running 1.2.0 on Ubuntu 10.04.
I use Fog primarily to take images of workstations for backup purposes. In the past few weeks I’ve noticed some uploaded images are disappearing from the server. I keep a log with dates and sizes so I know they were uploaded, but the /images subdirectory and files for those images are just gone.
About a month ago I had to rebuild the RAID after a failed drive, and I think it’s something to do with that rather than with my Fog installation. I’m about to remove and rebuild the array and start over completely (and probably move to CentOS), but before I do that I thought I’d check to see if anyone else has experienced anything like this. Maybe I’m missing something.
Thanks for any help.
-
RE: Speed Issue after upgrading to 1.1.0
Yep, changing that made a great difference in the speed, now I just have to find the happy medium between bandwidth and size. Thanks!
-
Speed Issue after upgrading to 1.1.0
I updated from .32 to 1.1.0 today, and everything went smoothly. I deployed an image with no problems and at a reasonable speed. But I’m running into issues uploading an image: on partition sda3 of my test system, the rate drops to ~500MB/min. I get 2-3GB/min uploading the other partitions and deploying an image.
I tried a few different kernels, same issue. I changed the image type to Multiple Partition Image - Single Disk (not resizable), because I think my images all defaulted to “MPI - All disks” after the upgrade, but no change. On the Image Management screen, the image size on client is 232.11GB, but the upload screen on the client shows space in use is ony 51.3 GB and my previous upload on .32 of the same image was only 18.5GB in storage.
Any ideas?
-
RE: Can't connect to NFS share on NAS storage
Still no luck. [FONT=Arial][COLOR=#333333] I manged to get the webui to recognize the NAS share and even begin to replicate the images there, but I ran into the same NFS error when I try to upload.[/COLOR][/FONT]
[COLOR=#333333][FONT=Arial]So I mounted the share as /images through this /etc/fstab:[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]10.0.71.38:/volume1/fogimages /images nfs defaults 0 0[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]/etc/exports:[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]/images *(rw,async,insecure,no_root_squash,subtree_check)[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]/images/dev *(rw,async,insecure,no_root_squash,subtree_check)[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]I chmodded and chowned the folders as follows:[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]fog@GPFOG:~$ ls -l /images[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]drwxrwxrwx 2 fog root 4096 2014-03-24 14:53 dev[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]drwxrwxrwx 4 fog root 4096 2014-03-24 13:50 images[/FONT][/COLOR]
[COLOR=#333333][FONT=Arial]I’m still getting the Permission denied, Fatal error:failed to mount NFS volume when I try to upload an image. The .mntcheck files are in place in /images and /images/dev. I’ve spent hours looking for a solution, but everything I find doesn’t work. I get that Synology NASes share as /volume1/SHARENAME but just /SHARENAME for FTP, but I don’t know if that’s the issue or what to do about it if it is.[/FONT][/COLOR] -
RE: Can't connect to NFS share on NAS storage
Exports:
/volume1/fogimages *(rw,async,no_wdelay,no_root_squash,insecure,sec=sys,anonuid=1025,anongid=100)ls -l /volume1/fogimages
drwxrwxrwx 2 fog administ 4096 Mar 12 11:05 devI changed to:
drwxrwxrwx 2 root root 4096 Mar 12 11:05 dev
But it’s still not working. I haven’t tried restarting the NAS yet, so I’ll do that next.
Thanks for the help.
-
RE: Can't connect to NFS share on NAS storage
[FONT=Arial][COLOR=#333333]Just an update: [/COLOR][/FONT]
[FONT=Arial][COLOR=#333333][FONT=Arial][COLOR=#000000]I’ve beat my head against this for two days.[/COLOR][/FONT][/COLOR][/FONT]
[FONT=Arial][COLOR=#333333]I enabled NFS on the NAS, created a share and a user and gave the user permissions. I’ve set up NFS privileges on the share, but it still keeps failing to connect when I try to add the storage node through the webUI. [/COLOR][/FONT]
[FONT=Arial][COLOR=#333333]I can mount the share from the terminal on the FOG server, so I know it’s working. I’ve tried messing around with /etc/exports files, changing UIDs and GIDs, deleting and recreating folders and users, reinstalling the fog server, etc. and nothing is working. [/COLOR][/FONT]
[FONT=Arial][COLOR=#333333]I also tried mounting the share on the FOG server and just pointing the storage node there, and that sort of works, but I get all kinds of NFS permissions issues when I try to upload or deploy an image. It’s mounted RW in the /etc/fstab, but it still can’t write there for some reason. And I can’t chmod or chown the directory, even as root – it says operation not permitted.[/COLOR][/FONT]
[FONT=Arial][COLOR=#333333] If it won’t work with the NAS I guess the other option is to make a VM (or physical box) with more storage and install fog as a storage node. [/COLOR][/FONT]