Site

Advanced Format Drives

Site.AdvancedFormatDrives History

Hide minor edits - Show changes to output

Added line 9:
Added line 1:
\\
Changed lines 3-5 from:
The 512e (emulated) hard drives always report 512 even though the actual physical sector size is 4Kib. This is problematic for a file system like ZFS which doesn’t have static block sizes. Without intervention, ZFS would incorrectly assume that it could atomically and efficiently access data in units of 512 bytes. In addition to the 512e obfuscation, we have discovered that some USB and Firewire bridges also hide the true native sector size.
to:
The 512e (emulated) hard drives always report 512 even though the actual physical sector size is 4Kib. This is problematic for a file system like ZFS which doesn’t have static block sizes. Without intervention, ZFS would incorrectly assume that it could atomically and efficiently access data in units of 512 bytes.

In addition to the 512e obfuscation, we have discovered that some USB and Firewire bridges also hide the true native sector size.
Changed lines 13-16 from:
->@@ashift: 12@@\\
->@@ashift: 12@@\\
->@@ashift: 12@@\\
->@@ashift: 12@@
to:
@@ashift: 12@@\\
@@ashift: 12@@\\
@@ashift: 12@@\\
@@ashift: 12@@
Changed lines 13-16 from:
@@ashift: 12@@\\
@@ashift: 12@@\\
@@ashift: 12@@\\
@@ashift: 12@@\\
to:
->@@ashift: 12@@\\
->@@ashift: 12@@\\
->@@ashift: 12@@\\
->@@ashift: 12@@
Changed lines 12-16 from:
@@$ sudo zdb -l /dev/rdisk2s2 | grep ashift@@
@@ashift: 12@@
@@ashift: 12@@
@@ashift: 12@@
@@ashift: 12@@
to:
@@$ sudo zdb -l /dev/rdisk2s2 | grep ashift@@\\
@@ashift: 12@@\\
@@ashift: 12@@\\
@@ashift: 12@@\\
@@ashift: 12@@\\
Changed lines 13-16 from:
@@ ashift: 12@@
@@ ashift: 12@@
@@ ashift: 12@@
@@
ashift: 12@@
to:
@@ashift: 12@@
@@ashift:
12@@
@@ashift: 12@@
@@ashift: 12@@
Added line 4:
Changed lines 12-16 from:
$ sudo zdb -l /dev/rdisk2s2 | grep ashift
ashift: 12
ashift: 12
ashift: 12
ashift: 12
to:
@@$ sudo zdb -l /dev/rdisk2s2 | grep ashift@@
@@
ashift: 12@@
@@
ashift: 12@@
@@
ashift: 12@@
@@
ashift: 12@@
Changed line 4 from:
to:
----
Changed line 7 from:
$ sudo zpool create -o ashift=12 tank mirror /dev/disk2 /dev/disk4
to:
@@$ sudo zpool create -o ashift=12 tank mirror /dev/disk2 /dev/disk4@@
Changed line 1 from:
There are two types of [[http://en.wikipedia.org/wiki/Advanced_Format | Advanced Format]] drives: '''512 emulation''' (512e) and '''4K native''' (4Kn). The ZEVO implementation supports both. However, 512 emulation drives need to be identified by passing the ashift=12 property when using the ''zpool create'' command.
to:
There are two types of [[http://en.wikipedia.org/wiki/Advanced_Format | Advanced Format]] drives: '''512 emulation''' (512e) and '''4K native''' (4Kn). The ZEVO implementation supports both. However, 512 emulation drives need to be identified by passing the ''ashift=12'' property when using the ''zpool create'' command.
Changed lines 3-5 from:
The 512e (emulated) hard drives always report 512 even though the actual physical sector size is 4Kib. This is problematic for a file system like ZFS which doesn’t have static block sizes. Without intervention, ZFS would incorrectly assume that it could atomically and efficiently access data in units of 512 bytes.
For additional info regarding Advanced Format see: http://en.wikipedia.org/wiki/Advanced_Format
In addition to the 512e obfuscation, we have discovered that some USB and Firewire bridges also hide the true native sector
size.
to:
The 512e (emulated) hard drives always report 512 even though the actual physical sector size is 4Kib. This is problematic for a file system like ZFS which doesn’t have static block sizes. Without intervention, ZFS would incorrectly assume that it could atomically and efficiently access data in units of 512 bytes. In addition to the 512e obfuscation, we have discovered that some USB and Firewire bridges also hide the true native sector size.
Changed line 1 from:
There are two types of [[Advanced Format | http://en.wikipedia.org/wiki/Advanced_Format]] drives: 512 emulation (512e) and 4K native (4Kn). The ZEVO implementation supports both. However, 512 emulation drives need to be identified by passing the ashift=12 property when using the ''zpool create'' command.
to:
There are two types of [[http://en.wikipedia.org/wiki/Advanced_Format | Advanced Format]] drives: '''512 emulation''' (512e) and '''4K native''' (4Kn). The ZEVO implementation supports both. However, 512 emulation drives need to be identified by passing the ashift=12 property when using the ''zpool create'' command.
Added lines 1-16:
There are two types of [[Advanced Format | http://en.wikipedia.org/wiki/Advanced_Format]] drives: 512 emulation (512e) and 4K native (4Kn). The ZEVO implementation supports both. However, 512 emulation drives need to be identified by passing the ashift=12 property when using the ''zpool create'' command.

The 512e (emulated) hard drives always report 512 even though the actual physical sector size is 4Kib. This is problematic for a file system like ZFS which doesn’t have static block sizes. Without intervention, ZFS would incorrectly assume that it could atomically and efficiently access data in units of 512 bytes.
For additional info regarding Advanced Format see: http://en.wikipedia.org/wiki/Advanced_Format
In addition to the 512e obfuscation, we have discovered that some USB and Firewire bridges also hide the true native sector size.
The following command will set the ashift value to 12 as expected for a 4096 native sector size:

$ sudo zpool create -o ashift=12 tank mirror /dev/disk2 /dev/disk4

You can verify the results (ashift = 12) using the zdb -l command, as follows:

$ sudo zdb -l /dev/rdisk2s2 | grep ashift
ashift: 12
ashift: 12
ashift: 12
ashift: 12

Green Marinee theme adapted by David Gilbert, powered by PmWiki