ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XenServer 6.5 - SR "Run out of space while coalescing."

    Scheduled Pinned Locked Moved IT Discussion
    xen3parxenserversanvirtualizationstorage
    15 Posts 4 Posters 6.9k Views
    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.
    • scottalanmillerS
      scottalanmiller
      last edited by

      Are there a lot of snaps in that pool?

      1 Reply Last reply Reply Quote 2
      • scottalanmillerS
        scottalanmiller
        last edited by

        Some interesting stuff in here: http://discussions.citrix.com/topic/347002-how-to-fix-vhd-coalesce-mess-in-xenserver-62

        From the article, try some of these when this happens and let's see if there is something happening trying to clean things up:

        tail (or cat, if you like) /var/log/SMlog | grep -i "exception"
        tail (or cat, if you like) /var/log/SMlog | grep -i "coalesced"
        tail (or cat, if you like) /var/log/SMlog | grep -i "kicking"
        tail (or cat, if you like) /var/log/SMlog | grep "GC"
        
        1 Reply Last reply Reply Quote 1
        • scottalanmillerS
          scottalanmiller
          last edited by

          My guess is that there are many snaps and a ton of space is used during the coalesce phase and it then clears up before you are checking it so that it appears like there is a lot of space but it actually runs out at some point momentarily.

          1 Reply Last reply Reply Quote 0
          • DustinB3403D
            DustinB3403
            last edited by

            Sorry did this ever get addressed? Did you check for any dis-associated vDisk that you can delete?

            1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller
              last edited by

              Oh yeah, I forgot that we were waiting for him to get back to us on this.

              1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller
                last edited by

                He had a thread on SW that did not get as much traffic but had two responses but went silent too...

                http://community.spiceworks.com/topic/1242191-xenserver-6-5-sr-run-out-of-space-while-coalescing

                He's not been on here for nine days.

                1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  Just checked, he went quiet on SW the same day, nine days ago. I sent him a PM, hope that all is okay.

                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    I checked in, he's just been too busy with a new rollout to revisit this.

                    1 Reply Last reply Reply Quote 0
                    • anthonyhA
                      anthonyh
                      last edited by anthonyh

                      Hey all - So sorry for going dead! We implemented a new system that basically "runs the organization" and it's been a mad house. We consolidated 6 separate databases into one system, and even after a year of doing data migration tests, UAT, etc., it's still a bit of a mess (which we anticipated, fortunately). In any rate, I am here to update this thread on the issue...

                      It seems that the issue was caused by my backup software. Because the backup jobs were taking so long to process, for one magical moment, the software would have snapshots created for every single VM. This was the cause of the issue. After beefing up our backup server and adding SSDs for the metadata database (deduplication), backup windows are MUCH better, jobs are not overlapping as much as before, and this issue has not happened since.

                      Thanks everyone for the help! I'm hoping to be able to participate a bit more moving forward. We'll see how that goes... 😄

                      1 Reply Last reply Reply Quote 5
                      • scottalanmillerS
                        scottalanmiller
                        last edited by

                        Awesome, glad that you managed to find a solution!

                        1 Reply Last reply Reply Quote 0
                        • JaredBuschJ
                          JaredBusch
                          last edited by

                          Looks like it was snapshots as @scottalanmiller was finding. Good to know.

                          anthonyhA 1 Reply Last reply Reply Quote 1
                          • anthonyhA
                            anthonyh @JaredBusch
                            last edited by

                            @JaredBusch I suspected the same as well, but what was confusing was that they would be cleaned up by the time I would be able to troubleshoot. It seemed to be a very short moment where it would happen, as it seemed to happen long enough for XenCenter to alert, but not long enough to have any impact on the environment.

                            1 Reply Last reply Reply Quote 0
                            • scottalanmillerS
                              scottalanmiller
                              last edited by

                              So many things use snapshots under the hood, space can grow and shrink pretty rapidly in confusing ways.

                              1 Reply Last reply Reply Quote 1
                              • 1 / 1
                              • First post
                                Last post