Uploading to wrong storage group

[Wayne Workman]

@dolf I’m specifically talking about the images storage group. You’ve not posted a picture of that. Click the image, on the left is storage groups.

[dolf]

Sorry, I wasn’t aware that an image can belong to more than one storage group. The relevant images were in one group (olifant), but it wasn’t marked as primary. It is marked primary now. The same error shows up when trying to deploy:

Note that I did not sensor anything in that image. There are no hosts listed…

[Wayne Workman]

@dolf it could be that the image uploaded to /images instead of the correct directory. Can you check? ls -lahRt /images

[dolf]

Files are in the right places, IMO:

$ tree /mnt/olifant/images/
/mnt/olifant/images/
├── 20160127Temp
│   ├── d1.fixed_size_partitions
│   ├── d1.original.fstypes
│   ├── d1.original.partitions
│   ├── d1.original.swapuuids
│   ├── rec.img.000
│   └── sys.img.000
├── 20160706W7PreSysprep
│   ├── d1.fixed_size_partitions
│   ├── d1.mbr
│   ├── d1.minimum.partitions
│   ├── d1.original.fstypes
│   ├── d1.original.swapuuids
│   ├── d1p1.img
│   ├── d1p2.img
│   └── d1.partitions
├── 20160707W7PreSysprep
│   ├── d1.fixed_size_partitions
│   ├── d1.mbr
│   ├── d1.minimum.partitions
│   ├── d1.original.fstypes
│   ├── d1.original.swapuuids
│   ├── d1p1.img
│   ├── d1p2.img
│   └── d1.partitions
├── box20150731
│   ├── d1.fixed_size_partitions
│   ├── d1.original.fstypes
│   ├── d1.original.partitions
│   ├── d1.original.swapuuids
│   ├── rec.img.000
│   └── sys.img.000
├── dev
├── lab2win720150409
│   ├── d1.fixed_size_partitions
│   ├── d1.original.fstypes
│   ├── d1.original.partitions
│   ├── d1.original.swapuuids
│   ├── rec.img.000
│   └── sys.img.000
├── lab2win720150410
│   ├── d1.fixed_size_partitions
│   ├── d1.original.fstypes
│   ├── d1.original.partitions
│   ├── d1.original.swapuuids
│   ├── rec.img.000
│   └── sys.img.000
├── lab420150716
│   ├── d1.fixed_size_partitions
│   ├── d1.original.fstypes
│   ├── d1.original.partitions
│   ├── d1.original.swapuuids
│   ├── rec.img.000
│   └── sys.img.000
├── thin20150801
│   ├── d1.fixed_size_partitions
│   ├── d1.original.fstypes
│   ├── d1.original.partitions
│   ├── d1.original.swapuuids
│   ├── rec.img.000
│   └── sys.img.000
└── Win7noDriversnoDefaultUser
    ├── rec.img.000
    └── sys.img.000

$ tree /images
/images
├── 20160128W7PreSysprep
│   ├── d1.fixed_size_partitions
│   ├── d1.original.fstypes
│   ├── d1.original.partitions
│   ├── d1.original.swapuuids
│   ├── rec.img.000
│   └── sys.img.000
├── 20160129W7PostSysprep
│   ├── d1.fixed_size_partitions
│   ├── d1.original.fstypes
│   ├── d1.original.partitions
│   ├── d1.original.swapuuids
│   ├── rec.img.000
│   └── sys.img.000
├── dev
├── postdownloadscripts
│   └── fog.postdownload
└── Windows7Software
    ├── rec.img.000
    └── sys.img.000

[Wayne Workman]

@dolf in your first post, you said you manually moved the image. Tree doesn’t show the permissions, which could be suspect. Please check those.

[dolf]

It actually does, using color, which obviously didn’t survive the copy paste. Here is the output with permissions (I already did chmod -R 777 * )

$ ls -lha /images
total 28K
drwxrwxrwx  7 root root 4,0K Jul  9 10:57 .
drwxr-xr-x 28 root root 4,0K Jul  9 11:11 ..
drwxrwxrwx  2 fog  fog  4,0K Jan 29 02:42 20160128W7PreSysprep
drwxrwxrwx  2 fog  fog  4,0K Jan 29 13:10 20160129W7PostSysprep
drwxrwxrwx  2 root root 4,0K Jul  9 19:37 dev
-rwxrwxrwx  1 root root    0 Jan 27 16:13 .mntcheck
drwxrwxrwx  2 root root 4,0K Mar 23 14:43 postdownloadscripts
drwxrwxrwx  2 fog  fog  4,0K Jul  7  2015 Windows7Software

$ ls -lha /mnt/olifant/images/
total 48K
drwxrwxrwx 12 root root 4,0K Jul  7 21:43 .
drwxr-xr-x  5 root root 4,0K Mar 23 18:01 ..
drwxrwxrwx  2 root root 4,0K Jan 27 16:16 20160127Temp
drwxrwxrwx  2 root root 4,0K Jul  7 10:45 20160706W7PreSysprep
drwxrwxrwx  2 root root 4,0K Jul  7 20:57 20160707W7PreSysprep
drwxrwxrwx  2 root root 4,0K Aug  1  2015 box20150731
drwxrwxrwx  2 root root 4,0K Jul  9 19:38 dev
drwxrwxrwx  2 root root 4,0K Apr  9  2015 lab2win720150409
drwxrwxrwx  2 root root 4,0K Apr 10  2015 lab2win720150410
drwxrwxrwx  2 root root 4,0K Jul 31  2015 lab420150716
-rwxrwxrwx  1 root root    0 Jan 27 16:13 .mntcheck
drwxrwxrwx  2 root root 4,0K Aug  1  2015 thin20150801
drwxrwxrwx  2 root root 4,0K Jan 26 15:45 Win7noDriversnoDefaultUser

[Wayne Workman]

@dolf said in Uploading to wrong storage group:

/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)
/mnt/olifant/images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/mnt/olifant/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

That’s the problem I think (or at least one of them).

fsid cannot have duplicates.

You have: 0,1,0,1
They should be: 0,1,2,3

[dolf]

Changed fsids as suggested, and rebooted. No change. To be honest, I have not worked with NFS before. Thanks for the help thus far.

[Wayne Workman]

@dolf Does tree list hidden files? The command I posted does. You should have these files in these directories:
/mnt/olifant/images/.mntcheck
/mnt/olifant/images/dev/.mntcheck
/images/.mntcheck
/images/dev/.mntcheck

[dolf]

A few posts ago, I did post the output of ls - lha which shows the existence of .hidden files. They are present with the right permissions, IMO, but I pasted the output in case I overlook something.

[Wayne Workman]

Also - temporarily disable the Koei (root) storage node. It’s a check box in it’s settings.

Then see what happens.

[dolf]

No change when disabling koei. Also disabled olifant, tried again, enabled one and tried again, then both and tried again. No change.

[Wayne Workman]

@dolf Why does the olifant node have the directory /mnt/... ? In it’s description, you say it’s in lab2-server, is that the fog server or another server? Have you mounted a remote directory to the fog server?

[dolf]

I have only one physical Ubuntu machine running fog, with two hard drives. There is a storage node on each, belonging to different storage groups, so that I don’t have to have all of the images on one disk (not enough space). /mnt/olifant is simply the mount point for a physical 1.5TB internal SATA drive with one ext4 partition.

[Wayne Workman]

@dolf Ok. I’m about out of ideas then.

I’m going to need to ask for the help of @Tom-Elliott, @Moderators and @Testers for ideas.

[george1421]

@Wayne-Workman TBH I did not read the entire thread so if this has already been asked my apologies,

What is the results of showmount -e 127.0.0.1?

======
OP: If I understand this correctly you only have one FOG server but you have 2 hard drives in this physical server with each not having enough space for all of your images, do I understand this right? If so I think I would take a little different and less complex approach. There is two routes I can think of

1. Setup LVM and just add those disks to an LVM volume group and then create a LVM logical volume. Let LVM decide where to span the files on those two physical disks. Temp mount that LVM volume over /mnt and then move the content of /images to that LVM volume. Unmount /mnt and remount that new LVM volume over /images and be done with it. (make sure you update fstab). That way you are running a standard FOG configuration without having to deviate from the norm.
2. On your existing FOG server create 2 directories under /images like olifant and koei. Mount those two drives over those directories. Then when you create your image definitions make sure you pick one of the two drives. So if you create an image name called WIN7X64 make sure the destination path isn’t /images/WIN7X64 but /images/koei/WIN7X64 instead. Its not as clean as doing it at the OS level as with LVM but it should work.

[dolf]

# showmount -e 127.0.0.1
Export list for 127.0.0.1:
/mnt/olifant/images/dev *
/mnt/olifant/images     *
/images/dev             *
/images                 *

Thanks for the workaround ideas. Although I think we still have to solve the bug… If I apply a workaround, I won’t be able to help you find the bug.

Are there any success stories of having two nodes on one machine? Is it even supported?

[dolf]

If I add the image to the koei storage group as well, will it be copied (replicated) from /mnt/olifant/images/ to /images/ ? I could try that, remove it from the olifant group, and then add it again?

[Quazz]

@dolf I think you’re on to something there. The problem might be caused by the fact that the nodes are using the same interface.

To be honest, I’ve not seen this specific use case before, so I’m just guessing.

[Wayne Workman]

I’m curious if that 1.5TB drive can hold everything… if so, do away with the other node.