• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Images files duplicating themselves

Scheduled Pinned Locked Moved
FOG Problems
2
4
611
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    Julianh
    last edited by Quazz Jun 8, 2018, 3:22 AM Jun 7, 2018, 5:55 PM

    I have a fog 1.50 server. It’s been fine, as I’ve just been using it to deploy one set of images. I have a SSD Array for the boot device, and /images.

    I found I needed a bit more storage for some odd servers I needed, which could be a slow deployment, so I added a 5TB SATA drive as /images2.

    I had to rebuild the images in /images , they are 103 GB in size on the disk, 447GB on the client. They are raw, single disk images.

    The problem is I seem to be getting versions of the images on /images in /images2 here’s a copy from putty

    image@fog:/images$ ls
    dev                Linux-KM-Server5     Server3-VMware6.5
    images2-5TB        Linux-KM-Server6     Server4-VMware6.5
    Linux-KM-Server0   Linux-KM-Server7     Server5-VMware6.5
    Linux-KM-Server1   Linux-KM-Server8     Server6-VMware6.5
    Linux-KM-Server10  lost+found           Server7-VMware6.5
    Linux-KM-Server11  postdownloadscripts  Server8-VMware6.5
    Linux-KM-Server2   Server0-VMware6.5    Temp-S10-Waitingforspace
    Linux-KM-Server3   Server10-VMware6.5   Temp-S11
    Linux-KM-Server4   Server2-VMware6.5    vRoom1-ESXi-Guacamole
    
    image@fog:/images$ ls /images2
    backup-copy        Linux-KM-Server5     Server2-VMware6.5
    dev                Linux-KM-Server6     Server3-VMware6.5
    images2-5TB        Linux-KM-Server7     Server4-VMware6.5
    Linux-KM-Server0   Linux-KM-Server8     Server5-VMware6.5
    Linux-KM-Server1   lost+found           Server6-VMware6.5
    Linux-KM-Server10  postdownloadscripts  Server7-VMware6.5
    Linux-KM-Server11  Server0-VMware6.5    Server8-VMware6.5
    Linux-KM-Server2   Server10-VMware6.5   Temp-S10-Waitingforspace
    Linux-KM-Server3   Server11-VMware6.5   Temp-S11
    Linux-KM-Server4   Server1-VMware6.5    vRoom1-ESXi-Guacamole
    image@fog:/images$
    

    The actual directories contain the following;

    image@fog:/images$ ls -l Server0-VMware6.5/
    total 100958896
    -rwxrwxrwx 1 root root 103381871523 Jun  6 21:04 Server0-VMware6.5.000
    
    image@fog:/images$ ls -l /images2/Server0-VMware6.5/
    total 1421388
    -rw-r--r-- 1 fog root 1455495892 Mar 21 20:00 Server0-VMware6.5.000
    image@fog:/images$
    

    Can anyone guide me as to what’s happening, and what I can delete. I don’t have enough space left to actually image up the servers.

    Thanks

    Julian

    1 Reply Last reply Reply Quote 0
    • J
      Julianh
      last edited by Jun 8, 2018, 8:35 AM

      A thought, could I have somehow set up the 2 disks are storage nodes reaplicating between themselves?

      I’ve had a look but can;t find the option, any suggestions?

      Thanks

      Julian

      G 1 Reply Last reply Jun 8, 2018, 10:09 AM Reply Quote 0
      • G
        george1421 Moderator @Julianh
        last edited by Jun 8, 2018, 10:09 AM

        @julianh You can test your idea about replication by creating a second storage group then move your /images2 storage node to that second storage group. FOG will only replicate from the master node to storage nodes in the same storage group.

        Also what is the output of the df -h command. This will tell us how the file system is configured.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • J
          Julianh
          last edited by george1421 Jun 8, 2018, 3:05 PM Jun 8, 2018, 5:40 PM

          Thanks George,
          df -h gives

          image@fog:~$ df -h
          Filesystem                Size  Used Avail Use% Mounted on
          udev                      7.4G     0  7.4G   0% /dev
          tmpfs                     1.5G  8.9M  1.5G   1% /run
          /dev/mapper/fog--vg-root  1.9T  1.8T   39G  98% /
          tmpfs                     7.4G     0  7.4G   0% /dev/shm
          tmpfs                     5.0M     0  5.0M   0% /run/lock
          tmpfs                     7.4G     0  7.4G   0% /sys/fs/cgroup
          /dev/sda1                 472M   58M  390M  13% /boot
          /dev/sdb1                 4.6T  3.8T  549G  88% /images2
          tmpfs                     1.5G     0  1.5G   0% /run/user/1000
          

          As you can see there’s not a lot of space left on the first drive.
          I’ll be using th eimages for the next 3 weeks, even if they are not ideal, so I son’t want to create a new storage group in case I lose the images. the storage groups are;

          0_1528474518141_Storage nodes.jpg 0_1528474532470_storage group.jpg

          What would you suggest?

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          1 / 1
          • First post
            2/4
            Last post

          179

          Online

          12.2k

          Users

          17.3k

          Topics

          155.5k

          Posts
          Copyright © 2012-2024 FOG Project