Qourum disk running low on disk space

  • GilaMonster (10/7/2013)


    Jeff Moden (10/7/2013)


    our NetOps guys are apparently using the quorum drive to transfer data to our warm DR site.

    Oh my, that is horrid cluster design. Nothing but nothing should ever go onto the quorum.

    The quorum drive is only responding to what is changing on the SAN drives.

    Shouldn't be doing that. There should be no impact on the quorum from the other drives. It's not a staging drive for other cluster drives, all it should be is there to 'arbitrate' ownership of the cluster

    Heh... that's likely why things have been such a problem in the past. Thanks, Gail. I wasn't going to get involved in the problem but now it looks like I'll have to.

    --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.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Jeff Moden (10/8/2013)


    Heh... that's likely why things have been such a problem in the past. Thanks, Gail. I wasn't going to get involved in the problem but now it looks like I'll have to.

    Ping Allen, Denny or Geoff if you need more advice. What I know about clusters is dangerous.

    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
  • GilaMonster (10/8/2013)


    Jeff Moden (10/8/2013)


    Heh... that's likely why things have been such a problem in the past. Thanks, Gail. I wasn't going to get involved in the problem but now it looks like I'll have to.

    Ping Allen, Denny or Geoff if you need more advice. What I know about clusters is dangerous.

    Same here. I need to read up on it before I'd ping any of those folks. It's a bit embarassing to admit (I've always had a NetOps group that took care of things like clustering) that I know very little about clustering... probably not enough to be "dangerous". 😛 I at least have to learn the lingo of clusters so that I can actually understand what they might say so it's time for me to hit the books.

    Thanks again for your helpful suggestions, Gail.

    --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.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • The one thing is the RECYCLER... which you need to check and clear it out. But i doubt, it will allow you . I do not see files much space used by the cluster files. You can still remove old cluster and DTC files. If you want to be safer... do take back-up.

  • Thanks for your suggestions

  • Gerard Silveira (10/7/2013)


    Here is the directory listing

    The Quorum drive has 1GB space assigned to it

    Volume in drive Q is SQLRDM02-Quorum00

    Volume Serial Number is

    Directory of Q:

    10/07/2013 08:11 PM <DIR> MSCS

    06/23/2009 03:50 PM <DIR> MSDtc

    09/09/2012 09:06 AM <DIR> RECYCLER

    05/31/2012 09:19 AM <DIR> System Volume Information

    0 File(s) 0 bytes

    Directory of Q:\MSCS

    10/07/2013 08:11 PM <DIR> .

    10/07/2013 08:11 PM <DIR> ..

    07/07/2009 12:48 PM <DIR> 1b82aa9a-0428-400a-ba2f-98db2cdfe3a9

    07/07/2009 07:30 PM <DIR> 36e30fb5-1862-490e-895d-c705e95661be

    07/07/2009 12:38 PM <DIR> 54f37c4e-2a4c-4514-bd5f-045513b78133

    07/07/2009 07:52 PM <DIR> 67bd7082-e6e2-4d39-8540-1c9597b68743

    09/10/2010 10:09 AM 57,344 chk2E3F.tmp

    10/07/2013 07:34 PM 57,344 chk5BE0.tmp

    07/07/2009 07:12 PM <DIR> f883705e-1b80-4f8a-b925-74bf622b7567

    06/23/2009 03:50 PM <DIR> f9670a20-d05a-40df-a6f2-f1e6e21022da

    10/07/2013 08:11 PM <DIR> MSDtc

    10/07/2013 07:34 PM 32,768 quolog.log

    3 File(s) 147,456 bytes

    Directory of Q:\MSCS\1b82aa9a-0428-400a-ba2f-98db2cdfe3a9

    07/07/2009 12:48 PM <DIR> .

    07/07/2009 12:48 PM <DIR> ..

    07/07/2009 12:48 PM 764 00000001.CPR

    1 File(s) 764 bytes

    Directory of Q:\MSCS\36e30fb5-1862-490e-895d-c705e95661be

    07/07/2009 07:30 PM <DIR> .

    07/07/2009 07:30 PM <DIR> ..

    07/07/2009 07:30 PM 764 00000001.CPR

    07/07/2009 07:30 PM 8,192 00000001.CPT

    10/07/2013 08:11 PM 12,288 00000002.CPT

    07/07/2009 07:30 PM 8,192 00000003.CPT

    07/07/2009 07:30 PM 8,192 00000004.CPT

    07/07/2009 07:30 PM 8,192 00000005.CPT

    07/07/2009 07:30 PM 8,192 00000006.CPT

    09/25/2013 09:15 AM 12,288 00000007.CPT

    8 File(s) 66,300 bytes

    Directory of Q:\MSCS\54f37c4e-2a4c-4514-bd5f-045513b78133

    07/07/2009 12:38 PM <DIR> .

    07/07/2009 12:38 PM <DIR> ..

    07/07/2009 12:38 PM 764 00000001.CPR

    1 File(s) 764 bytes

    Directory of Q:\MSCS\67bd7082-e6e2-4d39-8540-1c9597b68743

    07/07/2009 07:52 PM <DIR> .

    07/07/2009 07:52 PM <DIR> ..

    07/07/2009 07:51 PM 764 00000001.CPR

    07/07/2009 07:51 PM 8,192 00000001.CPT

    10/07/2013 08:12 PM 12,288 00000002.CPT

    07/07/2009 07:51 PM 8,192 00000003.CPT

    07/07/2009 07:51 PM 8,192 00000004.CPT

    07/07/2009 07:51 PM 8,192 00000005.CPT

    07/07/2009 07:51 PM 8,192 00000006.CPT

    09/17/2012 01:37 PM 12,288 00000007.CPT

    8 File(s) 66,300 bytes

    Directory of Q:\MSCS\f883705e-1b80-4f8a-b925-74bf622b7567

    07/07/2009 07:12 PM <DIR> .

    07/07/2009 07:12 PM <DIR> ..

    07/07/2009 07:12 PM 764 00000001.CPR

    1 File(s) 764 bytes

    Directory of Q:\MSCS\f9670a20-d05a-40df-a6f2-f1e6e21022da

    06/23/2009 03:50 PM <DIR> .

    06/23/2009 03:50 PM <DIR> ..

    06/23/2009 03:50 PM 764 00000001.CPR

    1 File(s) 764 bytes

    Directory of Q:\MSCS\MSDtc

    10/07/2013 08:11 PM <DIR> .

    10/07/2013 08:11 PM <DIR> ..

    0 File(s) 0 bytes

    Directory of Q:\MSDtc

    06/23/2009 03:50 PM <DIR> .

    06/23/2009 03:50 PM <DIR> ..

    06/23/2009 03:50 PM 4,194,304 MSDTC.LOG

    1 File(s) 4,194,304 bytes

    Directory of Q:\RECYCLER

    09/09/2012 09:06 AM <DIR> .

    09/09/2012 09:06 AM <DIR> ..

    09/09/2012 09:06 AM <DIR> S-1-5-21-1394358491-809983319-1777090905-4540

    10/13/2010 01:15 PM <DIR> S-1-5-21-1394358491-809983319-1777090905-4632

    09/06/2013 01:02 PM <DIR> S-1-5-21-1394358491-809983319-1777090905-500

    0 File(s) 0 bytes

    Directory of Q:\RECYCLER\S-1-5-21-1394358491-809983319-1777090905-4540

    09/09/2012 09:06 AM <DIR> .

    09/09/2012 09:06 AM <DIR> ..

    09/09/2012 09:06 AM 65 desktop.ini

    09/14/2012 01:21 AM 20 INFO2

    2 File(s) 85 bytes

    Directory of Q:\RECYCLER\S-1-5-21-1394358491-809983319-1777090905-4632

    10/13/2010 01:15 PM <DIR> .

    10/13/2010 01:15 PM <DIR> ..

    10/13/2010 01:15 PM 65 desktop.ini

    10/13/2010 06:01 PM 20 INFO2

    2 File(s) 85 bytes

    Directory of Q:\RECYCLER\S-1-5-21-1394358491-809983319-1777090905-500

    09/06/2013 01:02 PM <DIR> .

    09/06/2013 01:02 PM <DIR> ..

    09/06/2013 01:02 PM 65 desktop.ini

    09/27/2013 07:37 AM 20 INFO2

    2 File(s) 85 bytes

    Total Files Listed:

    30 File(s) 4,477,671 bytes

    40 Dir(s) 52,877,312 bytes free

    Firstly, don't share your quorum disk with the Distributed Transaction Coordinator, use a separate disk.

    Secondly, configure your cluster efficiently and remove the quorum disk and use either node majority if you have an odd number of nodes or a witness fileshare if you have an even number of nodes.

    The largest file there is the msdtc log that i can see but its only 4MB. Whats in the recycle bin have you checked?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • The cluster is based on windows server 2003 can I have a witness file share ? Also we have setup standard quorum since we have 2 nodes, this way we can at least tolerate failure of one node.

    Regarding the Recycler, cant see anything within it ... thanks for your input, will try setting up a separate disk for the distributed transaction coordinator, Is there a best practice that should be followed here, should this be a completely separate disk or can I share the disk containing the data files?

Viewing 7 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic. Login to reply