Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Qourum disk running low on disk space


Qourum disk running low on disk space

Author
Message
Gerard Silveira
Gerard Silveira
SSC Journeyman
SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)

Group: General Forum Members
Points: 82 Visits: 226
I have a multi instance sql server 2008 cluster running on windows server 2003. On the node that owns the quorum disk I keep getting messages that the quorum disk is running low on disk space. My question is whats cauing the quorum disk to fill up and how can I prevent the quorum disk form getting full

Thanks
Dhananjay-440114
Dhananjay-440114
SSC-Enthusiastic
SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)

Group: General Forum Members
Points: 127 Visits: 307
Check all the folders exists on Qouram Disk for space. Normally the size of Qouram should not be more then few MB's if there are not much of logs. You can check old logs and clear it in case that is not required. But i doubt, logs will cause space issue.
Gerard Silveira
Gerard Silveira
SSC Journeyman
SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)

Group: General Forum Members
Points: 82 Visits: 226
Thanks for your reply, however the strange part is when I view the quorum disk through windows explorer, I cannot see what is filling up the disk. I could try increasing the space available to the quorum drive but that's just a fix not a root cause solution. The quorum disk is on a SAN and the cluster nodes are virtualized, so even increasing disk space would need an outage but so far I haven't had any luck finding out what's steadily eating up disk space.
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45223 Visits: 39927
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.

My recommendation would be to run a server side trace for anything that takes too long or writes too much data. It's something that should be done once in a while even if it's not affecting quorum size.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Gerard Silveira
Gerard Silveira
SSC Journeyman
SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)

Group: General Forum Members
Points: 82 Visits: 226
Thanks for your reply Jeff, but Im unable to make the corelation between inefficient code and the quorum disk running low on disk space.
Would you be ableto elaborate on the connection between the two ?
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47311 Visits: 44392
Jeff Moden (10/5/2013)
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.


Why would that affect the cluster's quorum drive?


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Dhananjay-440114
Dhananjay-440114
SSC-Enthusiastic
SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)SSC-Enthusiastic (127 reputation)

Group: General Forum Members
Points: 127 Visits: 307
Jeff, I am wondering doing anything in your DB, changing Database recovery model or performance issue on DB has anything to do with Quorum Drive...Quorum Drive is Database for your cluster.. So think from the angle that why your Quorum Drive is filling up fast, have you placed any thing else there or Quorum server log is filling it up.
Gerard Silveira
Gerard Silveira
SSC Journeyman
SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)SSC Journeyman (82 reputation)

Group: General Forum Members
Points: 82 Visits: 226
@Dhananjay,
From Windows explorer the only directories I see are the MSCS and MSDTC, there is nothing else that I can see that could be steadily eating up the disk space on the quorum drive.
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45223 Visits: 39927
GilaMonster (10/7/2013)
Jeff Moden (10/5/2013)
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.


Why would that affect the cluster's quorum drive?


I didn't have anything to do with this setup so I don't have a sufficient understanding of the details but our NetOps guys are apparently using the quorum drive to transfer data to our warm DR site. If the pipe between here and the DR site can't keep up, then the data on the quorum drive just gets larger and larger. There was some tipping point where if it got too far behind, it would go into a rather dedicated transfer mode and that just crushed the server when it happened. I use past tense because they supposedly fixed the problem but I'm not sure what they did to fix it other than getting a better pipe between us and the DR site.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47311 Visits: 44392
Jeff Moden (10/7/2013)
GilaMonster (10/7/2013)
Jeff Moden (10/5/2013)
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.


Why would that affect the cluster's quorum drive?


Because everything that changes int these tables ends up going to the quorum drive.


If it does someone has badly configured that cluster. There should be nothing from SQL Server on the quorum drive. I don't even know if the quorum drive can be marked as a dependency of SQL, it should be off limits to everything but the cluster management itself.

All that should be on the quorum drive are logs and a few files put down by the cluster installation, it should never be used for anything else.


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search