asked
DBCC checkdb
We are getting below error,when we run DBCC Checkdb . Msg 1823, Level 16, State 2, Line 1 A database snapshot cannot be created because it failed to start. Msg 1823, Level 16, State 8, Line 1 A database snapshot cannot be created because it failed to start. Msg 5149, Level 16, State 3, Line 1 MODIFY FILE encountered operating system error 665(The requested operation could not be completed due to a file system limitation) while attempting to expand the physical file 'H:\MSSQL\Data\TeamDBO.mdf:MSSQL_DBCC7'. Msg 7928, Level 16, State 1, Line 1 The database snapshot for online checks could not be created. Either the reason is given in a previous error. The Db is in SAN and space allocated 1.2TB and free space available is 1.1TB. Kindly Provide me your valuable guidance. Thanks, Praful
The site works on votes. Please show any helpful answers by clicking on the thumbs up next to those answers. If one answer lead you to a solution indicate that by clicking on the the check mark next to that answer.
Don't forget to vote on the answers you've received and mark one as a solution.
My first thought would be disk space, but you say there's plenty. What version of SQL Server are you running? There is a [problem with SQL Server 2012][1] that is fixed in a cumulative update. I would examine the hardware. It could be an issue with the SAN configuration or you might be looking at a memory problem. Make sure your SAN supports sparse files. You could try running the DBCC using WITH TABLOCK to make it not use a snapshot and see if that gets you through. Also, check your default data locations on the server. It could be trying to use say, the C:\ drive, and there's not enough room there for the snapshot. [1]:
http://support.microsoft.com/kb/2688395/en-us
Thanks Grant. We are using SQL Server 2012 SP1 and the Default data location is H drive.When,I ran dbcc checkdb with tablock,it is running fine. I will check with our SAN Administator for any potential error on SAN Configuration. Thanks, Praful
Is the default data drive for the instance formatted as NTFS? I believe snapshots require an NTFS formatted drive. Do [either][1] of [these][2] apply to your situation? I don't think you ever said what version of Windows and SQL you are running. [1]:
http://support.microsoft.com/kb/2002606 [2]:
http://blogs.msdn.com/b/psssql/archive/2008/07/10/sql-server-reports-operating-system-error-1450-or-1452-or-665-retries.aspx
I found the answer to that here:
http://support.microsoft.com/kb/2002606 SQL Server 2008 R2 running on Windows Server 2008 R2. You can find additional information in KB 96735. In our case, there was plenty of drive space left for modification, but the number of modifications grew to the point where the operating system could no longer keep track and marked the database snapshot suspect.
17 People are following this question.
