Dirty Bit keeps getting set on SQL Server Logs Drive

Question

Post reply

Dirty Bit keeps getting set on SQL Server Logs Drive

Francis Thorne-479948

SSC Journeyman

Points: 91
More actions
June 9, 2014 at 5:57 am

#292155

Hi all,
Running a Windows Server 2008 - SQL Server 2008 R2 SP2 Cluster
Multiple SQL installs (services) running , but on one particular SQL install everytime the service fails over (due to patch of nodes etc) we see that an error is reported against the disk
"Cluster disk resource 'SQL Logs' indicates corruption for volume"
Chkdsk is automatically run to repair the drive before the disk resource is brought on-line, however chkdsk never finds any errors. We have even run a manual chkdsk on the drive but again no errors are found. The hardware guys are says there is nothing physical wrong with the disk
Does anybody have any thoughts on if Windows / SQL Server might be setting the Dirty Bit on closing the SQL resource for some reason ? We dont see this behaviour on any other instance of SQL we have installed.
Many thanks
Francis

Viewing 5 posts - 1 through 5 (of 5 total)

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

Jeff Moden SSC Guru Points: 1004646 More actions · Answer 1

Sorry, Francis... I've never seen such a thing but, hopefully, my reply will serve as a "bump" on this issue for you.

--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 SSC Guru Points: 1004646 More actions · Answer 2

Dunno if this helps, but my Assistant DBA (Mr. Google) found this...

http://support.microsoft.com/kb/321939

He also found a bunch of other things that you might want to take a look at. Here's the search I used...

https://www.google.com/#q=dirty+bit+set+on+failover

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

EdVassie SSC Guru Points: 60531 More actions · Answer 3

There is also a KB article about disk corruption being reported on a failover if the volume was formatted using a Quick Format and you are accessing it via iSCSI.

Although some of the problems reported do happen for real, I think there are also some false positives that are reported (my problem was a fp). Trying to find the root cause for a fp can be a long process, but certainly I learned a lot in the looking.

Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

Francis Thorne-479948 SSC Journeyman Points: 91 More actions · Answer 4

Apologies for the delay in response, many thanks for the informaton provided i should have some time today to read through the links provided.

Thanks again