1

Topic: Error 665 by operation with snapshot

Day kind.
Prompt  that it is possible to make with snapshot th that it periodically did not fall with an error 665.
The circuit such. There is the main 1 with oltp loading (a various and constant insertion of the data), a DB  on another 2, from a mirror in the mornings becomes  and already with it  users in a mode a-lja olap work, i.e. drive various reports. OS on both servers Win2012R2, SQL2016Enterprise also on both, on disks  NTFS, disks - through FC on  quite good level (EMC VNX5500), the size of a DB of the order 1.5, a record count in the biggest "problem" table - more 1.
The error looks like:
The operating system returned error 665 (The requested operation could not be completed due to a file system limitation) to A SQL Server during a write at offset 0x0000116fbf4000 in file ' D:\Snapshot\myDB.ss'.
Error: 17053, Severity: 16, State: 1.
And further:
SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 5:20340841; actual 0:0). It occurred during a read of page (5:20340841) in database ID 7 at offset 0x000026cc0d2000 in file ' D:\Snapshot\myORC.ss'
The error arises at various times, certainly while there are mass changes/inserts to a DB-source. Arose at night earlier, well when the data from remote platforms merged in the general DB, but that is not terrible, in the morning  anew formed. Recently even more often in flow of the working day.
That is important.  the DB-mirror lies on the same disk, as. On a disk it is enough place, from 3, a minimum 1.2 are always free. A maximum the size  to which grew for a day - 300-400.
With what to begin?  to transfer on a separate disk? To reduce file size, in which "problem" table (it here this file group myORC in which the error specifies)? There basically, is what to transfer, other tables, indexes...
Mirroring works without problems and errors, by the way.

2

Re: Error 665 by operation with snapshot

https://support.microsoft.com/en-us/hel … data-files

3

Re: Error 665 by operation with snapshot

It is possible to look at a file fragmentation quickly: https://docs.microsoft.com/en-us/sysint … ads/contig

4

Re: Error 665 by operation with snapshot

, it not that. The file  forms every day anew how it can be strong ? And OS informs nothing, ntfs.sys would swear

5

Re: Error 665 by operation with snapshot

JohnAl wrote:

And OS informs nothing

really?

wrote:

The operating system returned error 665 (The requested operation could not be completed due to a file system limitation) to a SQL Server during a write at offset 0x0000116fbf4000 in file ' D:\Snapshot\myDB.ss'.

6

Re: Error 665 by operation with snapshot

JohnAl wrote:

the File  forms every day anew how it can be strong ?

And at what here every day or not everyone?
I can create once a year , but not touch the data generally;
And I can and every day, but all basis .
It is necessary volume of changes given to look, instead of days of life  to count

7

Re: Error 665 by operation with snapshot

Well if real file size  on a disk - from 30 to 100 it is explicit not "all basis ". It is difficult to estimate kol-in changes in flow of day, but it is the order of several millions, instead of hundred million
The error report generates itself . OS as though also does not note a problem, additional errors are not present

8

Re: Error 665 by operation with snapshot

By the way  says that only 985 fragments on  a file . But it since morning is finite, while it empty. We look in flow of day...