Project

General

Profile

Actions

Bug #3969

open

zpool should not accept devices with a larger (incompatible) ashift

Added by Steven Hartland about 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
zfs - Zettabyte File System
Start date:
2013-08-02
Due date:
% Done:

0%

Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:

Description

https://www.illumos.org/issues/2671 added the ability to use a device which has a larger ashift that the pool was created with.

This is an invalid change as it allow the use of a device with a larger sector size than the pool can access.

I believe the change was actually designed to allow "faked" ashift increases as used to force devices which advertise their logical and physical sector sizes as 512b when in fact 4k native devices.

In that specific case this change will work but it will also allow a fully native 4k device to be used at which point it will fail as ZFS has no way to align reads and writes correctly.

Initially this change should be backed out and then ashift calculations updated to take into account two values, the minimum sector sizes of devices and the desired sector sizes of devices.

I have just such a change for FreeBSD but I'm looking to enhance it further with the ability to configure the "desired" value from the zpool command line.

No data to display

Actions

Also available in: Atom PDF