diff options
author | George Wilson <[email protected]> | 2012-05-03 05:49:19 -0700 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2012-11-15 11:05:59 -0800 |
commit | 32a9872bbae90a7cd9793c371f558701ec268976 (patch) | |
tree | 03ac598a158bd8559e4eaac5223252c84a274cc3 /config/.gitignore | |
parent | 3997bc74351d608e1a09f8ba8d58fb1c12fff331 (diff) |
Illumos #2671: zpool import should not fail if vdev ashift has increased
Reviewed by: Adam Leventhal <[email protected]>
Reviewed by: Eric Schrock <[email protected]>
Reviewed by: Richard Elling <[email protected]>
Reviewed by: Gordon Ross <[email protected]>
Reviewed by: Garrett D'Amore <[email protected]>
Approved by: Richard Lowe <[email protected]>
Refererces to Illumos issue:
https://www.illumos.org/issues/2671
This patch has been slightly modified from the upstream Illumos
version. In the upstream implementation a warning message is
logged to the console. To prevent pointless console noise this
notification is now posted as a "ereport.fs.zfs.vdev.bad_ashift"
event.
The event indicates a non-optimial (but entirely safe) ashift
value was used to create the pool. Depending on your workload
this may impact pool performance. Unfortunately, the only way
to correct the issue is to recreate the pool with a new ashift.
NOTE: The unrelated fix to the comment in zpool_main.c appears
in the upstream commit and was preserved for consistnecy.
Ported-by: Cyril Plisko <[email protected]>
Reworked-by: Brian Behlendorf <[email protected]>
Closes #955
Diffstat (limited to 'config/.gitignore')
0 files changed, 0 insertions, 0 deletions