{"id":755,"date":"2010-01-13T14:34:00","date_gmt":"2010-01-13T14:34:00","guid":{"rendered":"\/blogs\/paul\/post\/Diskeeper-10-Intelliwrite-corruption-bug.aspx"},"modified":"2017-04-13T09:54:04","modified_gmt":"2017-04-13T16:54:04","slug":"diskeeper-10-intelliwrite-corruption-bug","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/paul\/diskeeper-10-intelliwrite-corruption-bug\/","title":{"rendered":"Diskeeper 10 Intelliwrite corruption bug"},"content":{"rendered":"

\nA couple of years ago I <\/font>blogged about 3rd-party file system filter drivers<\/font><\/a> and how if they're not coded correctly to cope with NTFS alternate streams they will cause all kinds of weird corruption errors to be reported when DBCC CHECKDB is running. At the time I'd only seen the issue a couple of times so thought no more about it until a few weeks ago.<\/font>\n<\/p>\n

\nI was settling down to watch a movie with my laptop nearby when I got involved helping fellow-MVP Jonathan Kehayias (<\/font>blog<\/font><\/a>|<\/font>twitter<\/font><\/a>). As things progressed it dawned on me that his CHECKDBs were fine using regular database snapshots, but failed using the automatically-created snapshots, which use NTFS alternate streams (see <\/font>this blog post<\/font><\/a> where I explain about them). The errors produced were as below (borrowed from Jonathan's blog post):<\/font>\n<\/p>\n

\n

\n\t2009-12-10 01:35:44.04 spid75      Error: 17053, Severity: 16, State: 1.
\n\t2009-12-10 01:35:44.04 spid75      E:\\SQLData\\MSSQL.1\\DatabaseName.mdf:MSSQL_DBCC16: Operating system error 1784(The supplied user buffer is not valid for the requested operation.) encountered.
\n\t2009-12-10 01:35:44.07 spid98      DBCC CHECKDB (DatabaseName) WITH all_errormsgs, no_infomsgs, data_purity executed by Domain\\UserName found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 9 seconds.
\n\t2009-12-10 01:35:44.45 spid98      Error: 926, Severity: 21, State: 6.
\n\t2009-12-10 01:35:44.45 spid98      Database 'DatabaseName' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. <\/font> <\/font>\n\t<\/p>\n<\/blockquote>\n

\nLo-and-behold, it turned out to be a Diskeeper 10 filter driver that had a bug in it. You can read Jonathan's more in-depth recounting of the story on his blog <\/font>here<\/font><\/a>.<\/font>\n<\/p>\n

\nDiskeeper issued a fix a couple of weeks back, and Microsoft Product Support also put out a blog post with some details. Links are:<\/font>\n<\/p>\n