﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server 2008 - General  / The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset ... / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sun, 19 May 2013 05:27:54 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset ...</title><link>http://www.sqlservercentral.com/Forums/Topic1252840-391-1.aspx</link><description>Not sure whether you solved this or not, but you might want to review this Microsoft KB about a known Hotfix for the OS for the "'Operating system error 665'  BackupIoRequest::ReportIoError: " Or for anybody else who runs into this issue and might need it.[size="2"][b]OS Errors 1450 and 665 are reported for database data files[/b][/size]http://support.microsoft.com/kb/2002606</description><pubDate>Wed, 09 Jan 2013 09:45:05 GMT</pubDate><dc:creator>cannonphoder</dc:creator></item><item><title>RE: The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset ...</title><link>http://www.sqlservercentral.com/Forums/Topic1252840-391-1.aspx</link><description>It is quite possibly that the problem that I am having are related to "File System Filter Drivers":A tale of CHECKDB failures cause by 3rd party file-system drivershttp://sqlblog.com/blogs/jonathan_kehayias/archive/2009/12/10/a-tale-of-checkdb-failures-cause-by-3rd-party-file-system-drivers.aspxTwo Minute Drill: File System Filter Drivershttp://blogs.technet.com/b/askperf/archive/2008/08/08/two-minute-drill-file-system-filter-drivers.aspxSearch Engine Q&amp;A #14: Beware 3rd party file-system drivers with DBCC CHECKDBhttp://www.sqlskills.com/BLOGS/PAUL/post/Search-Engine-QA-14-Beware-3rd-party-file-system-drivers-with-DBCC-CHECKDB.aspxWhen I go in tomorrow, I will use the file extension mdf for my database snapshot files.  Currently, I chose touse .ss, but that is probably causing trouble with my Anti-Virus Software that is more likely than notonly filtering against mdf and ldf - It is probable that ndfs are skipped, as well.</description><pubDate>Wed, 15 Feb 2012 23:28:28 GMT</pubDate><dc:creator>Daniel Adeniji-180202</dc:creator></item><item><title>The operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset ...</title><link>http://www.sqlservercentral.com/Forums/Topic1252840-391-1.aspx</link><description>I am kind of in a bit of a Jam.Seeing a lot of Storage I/O issues.The OS is MS Windows 2008 R2 (RTM) and MS SQL Server 2008/R2 (RTM).Based on an analysis I did over the weekend (which is attached), we applied SP1 to both OS and SQL Server this morning.But, I am still not able to create Database Snapshots.  And, when I am able to create them, I get the following errors:Date		2/15/2012 11:37:53 PMLog		SQL Server (Current - 2/15/2012 11:39:00 PM)Source		spid22sMessageThe operating system returned error 665(The requested operation could not be completed due to a file system limitation) to SQL Server during a write at offset 0x0000123b0f0000 in file 'Z:\DATA\JPE_Snapshot.ss'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.</description><pubDate>Wed, 15 Feb 2012 20:27:59 GMT</pubDate><dc:creator>Daniel Adeniji-180202</dc:creator></item></channel></rss>