Article ID: 2624272
Microsoft distributes Microsoft SQL Server 2008 R2 Service Pack 1 (SP1) fixes in one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 R2 Service Pack 1 (SP1) update release.
Consider the following scenario:
In this scenario, an error 9013 which resembles the following might be logged in the SQL Server error log:
The tail of the log for database %ls is being rewritten to match the new sector size of %d bytes. %d bytes at offset %I64d in file %ls will be written.
Note This error causes no risk to the database.
This issue occurs because the logical sector size for the master, msdb, and model databases is not accommodated appropriately.
When a database is created, a logical sector size is stored in the metadata. When a database is brought online, a check is performed to see whether the data that is written in the log file is aligned with the sector size that is formatted. If they are not aligned, then the tail of the log will be rewritten and the issue that is mentioned in the "Symptoms" section occurs.
Based on the design from Microsoft SQL Server 2000, the master, model, and msdb databases are formatted with a sector size of 4096 bytes. The maximal value of physical sector size and logical sector size are used in versions of SQL Server earlier than SQL Server 2008 R2 SP1. However, SQL Server 2008 R2 SP1 adds support for 512-byte Emulation (512e) disk drives. Because of a defect, the physical sector size is used when it should not be. For example, if the physical sector size of the disk drive is 512 bytes and the logical sector size of the master, model, and msdb databases is 4096 bytes, then they are not aligned. Therefore, the error message that is mentioned in the "Symptoms" section is logged in the SQL Server error log.
Note Usually, it is the physical sector size of the disk drive on which the database is created.