Does SQL Server 2017, including older versions, support 8k disk sector sizes?












13















Disk (loosely worded to include not only rotational media but non-rotational media [SSD, NVMe, etc.]) drives are continuing to evolve in their underlying formats and hardware. Part of this was an "enhancement" from 512 byte physical sector sizes to 4k physical sector sizes, which changes the on disk layout (512n, 512e, 4kn).



This next evolution is in using 8k physical sector sizes, which some manufacturers are starting to produce and setup in production. Given this next step, is the 8k sector size disk supported in Windows? Does SQL Server care about sector sizes?










share|improve this question




















  • 8





    Welcome to the site! Please take the tour and enjoy your time here!

    – Joe Obbish
    7 hours ago
















13















Disk (loosely worded to include not only rotational media but non-rotational media [SSD, NVMe, etc.]) drives are continuing to evolve in their underlying formats and hardware. Part of this was an "enhancement" from 512 byte physical sector sizes to 4k physical sector sizes, which changes the on disk layout (512n, 512e, 4kn).



This next evolution is in using 8k physical sector sizes, which some manufacturers are starting to produce and setup in production. Given this next step, is the 8k sector size disk supported in Windows? Does SQL Server care about sector sizes?










share|improve this question




















  • 8





    Welcome to the site! Please take the tour and enjoy your time here!

    – Joe Obbish
    7 hours ago














13












13








13








Disk (loosely worded to include not only rotational media but non-rotational media [SSD, NVMe, etc.]) drives are continuing to evolve in their underlying formats and hardware. Part of this was an "enhancement" from 512 byte physical sector sizes to 4k physical sector sizes, which changes the on disk layout (512n, 512e, 4kn).



This next evolution is in using 8k physical sector sizes, which some manufacturers are starting to produce and setup in production. Given this next step, is the 8k sector size disk supported in Windows? Does SQL Server care about sector sizes?










share|improve this question
















Disk (loosely worded to include not only rotational media but non-rotational media [SSD, NVMe, etc.]) drives are continuing to evolve in their underlying formats and hardware. Part of this was an "enhancement" from 512 byte physical sector sizes to 4k physical sector sizes, which changes the on disk layout (512n, 512e, 4kn).



This next evolution is in using 8k physical sector sizes, which some manufacturers are starting to produce and setup in production. Given this next step, is the 8k sector size disk supported in Windows? Does SQL Server care about sector sizes?







sql-server hardware






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 8 hours ago









jadarnel27

5,94311938




5,94311938










asked 11 hours ago









Sean GallardySean Gallardy

16.5k22653




16.5k22653








  • 8





    Welcome to the site! Please take the tour and enjoy your time here!

    – Joe Obbish
    7 hours ago














  • 8





    Welcome to the site! Please take the tour and enjoy your time here!

    – Joe Obbish
    7 hours ago








8




8





Welcome to the site! Please take the tour and enjoy your time here!

– Joe Obbish
7 hours ago





Welcome to the site! Please take the tour and enjoy your time here!

– Joe Obbish
7 hours ago










1 Answer
1






active

oldest

votes


















12















Is the 8k sector size disk supported in Windows?




Currently, no, it is not supported by Windows and has been documented.




Does SQL Server care about sector sizes?




Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).



If you attempt to use a physical sector size above 4k (4096) you'll receive an error:



Msg 5179, Level 16, State 1, Line 1
Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.
SQL Server supports a maximum sector size of 4096 bytes.
Move the file to a volume with a compatible sector size.


In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.



Solution



If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.






share|improve this answer





















  • 1





    How did you get NTFS on that disk to produce the error message?

    – eckes
    6 hours ago






  • 2





    @eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.

    – jadarnel27
    5 hours ago











  • @eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.

    – Sean Gallardy
    3 hours ago











  • @SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.

    – eckes
    3 hours ago













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230973%2fdoes-sql-server-2017-including-older-versions-support-8k-disk-sector-sizes%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









12















Is the 8k sector size disk supported in Windows?




Currently, no, it is not supported by Windows and has been documented.




Does SQL Server care about sector sizes?




Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).



If you attempt to use a physical sector size above 4k (4096) you'll receive an error:



Msg 5179, Level 16, State 1, Line 1
Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.
SQL Server supports a maximum sector size of 4096 bytes.
Move the file to a volume with a compatible sector size.


In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.



Solution



If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.






share|improve this answer





















  • 1





    How did you get NTFS on that disk to produce the error message?

    – eckes
    6 hours ago






  • 2





    @eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.

    – jadarnel27
    5 hours ago











  • @eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.

    – Sean Gallardy
    3 hours ago











  • @SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.

    – eckes
    3 hours ago


















12















Is the 8k sector size disk supported in Windows?




Currently, no, it is not supported by Windows and has been documented.




Does SQL Server care about sector sizes?




Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).



If you attempt to use a physical sector size above 4k (4096) you'll receive an error:



Msg 5179, Level 16, State 1, Line 1
Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.
SQL Server supports a maximum sector size of 4096 bytes.
Move the file to a volume with a compatible sector size.


In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.



Solution



If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.






share|improve this answer





















  • 1





    How did you get NTFS on that disk to produce the error message?

    – eckes
    6 hours ago






  • 2





    @eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.

    – jadarnel27
    5 hours ago











  • @eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.

    – Sean Gallardy
    3 hours ago











  • @SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.

    – eckes
    3 hours ago
















12












12








12








Is the 8k sector size disk supported in Windows?




Currently, no, it is not supported by Windows and has been documented.




Does SQL Server care about sector sizes?




Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).



If you attempt to use a physical sector size above 4k (4096) you'll receive an error:



Msg 5179, Level 16, State 1, Line 1
Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.
SQL Server supports a maximum sector size of 4096 bytes.
Move the file to a volume with a compatible sector size.


In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.



Solution



If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.






share|improve this answer
















Is the 8k sector size disk supported in Windows?




Currently, no, it is not supported by Windows and has been documented.




Does SQL Server care about sector sizes?




Yes, SQL Server does care about sector sizes. In fact, SQL Server checks the underlying physical disk information as it has data structures and algorithms that work with current disk sector sizes for various reasons (data integrity, optimizations, etc.).



If you attempt to use a physical sector size above 4k (4096) you'll receive an error:



Msg 5179, Level 16, State 1, Line 1
Cannot use file 'S:FolderTestDB.mdf ', because it is on a volume with sector size 8192.
SQL Server supports a maximum sector size of 4096 bytes.
Move the file to a volume with a compatible sector size.


In this case, you can see that the error message is specifically telling you that the maximum sector size is 4096 (4k). This means that volume can't be used for SQL Server, and as noted above it wouldn't be supported in Windows either.



Solution



If you're receiving this error/issue, unfortunately you'll need to use a supported disk sector size such as 512 bytes or 4k. Other formats are unsupported and can't be used. You'll need to contact your hardware vendor for the Disk subsystem used and ask if there are any other options.







share|improve this answer














share|improve this answer



share|improve this answer








edited 6 hours ago









Paul White

52.7k14281456




52.7k14281456










answered 11 hours ago









Sean GallardySean Gallardy

16.5k22653




16.5k22653








  • 1





    How did you get NTFS on that disk to produce the error message?

    – eckes
    6 hours ago






  • 2





    @eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.

    – jadarnel27
    5 hours ago











  • @eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.

    – Sean Gallardy
    3 hours ago











  • @SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.

    – eckes
    3 hours ago
















  • 1





    How did you get NTFS on that disk to produce the error message?

    – eckes
    6 hours ago






  • 2





    @eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.

    – jadarnel27
    5 hours ago











  • @eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.

    – Sean Gallardy
    3 hours ago











  • @SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.

    – eckes
    3 hours ago










1




1





How did you get NTFS on that disk to produce the error message?

– eckes
6 hours ago





How did you get NTFS on that disk to produce the error message?

– eckes
6 hours ago




2




2





@eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.

– jadarnel27
5 hours ago





@eckes It was probably SQL Server on Linux - Sean loves SQL Server on Linux.

– jadarnel27
5 hours ago













@eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.

– Sean Gallardy
3 hours ago





@eckes Windows will let you format it. I don't if or what version of the Linux Kernel supports larger than 4k.

– Sean Gallardy
3 hours ago













@SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.

– eckes
3 hours ago







@SeanGallardy oh so you had a real 8k blocksize (non Boot) disk working with Windows? BTW On Linux you should be able to emulate a 8k drive with the new logical blocksize option of losetup -b with 4.14 kernels.

– eckes
3 hours ago




















draft saved

draft discarded




















































Thanks for contributing an answer to Database Administrators Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f230973%2fdoes-sql-server-2017-including-older-versions-support-8k-disk-sector-sizes%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

RAC Tourist Trophy