Please sign in to comment.
Illumos #2671: zpool import should not fail if vdev ashift has increased
Reviewed by: Adam Leventhal <firstname.lastname@example.org> Reviewed by: Eric Schrock <email@example.com> Reviewed by: Richard Elling <firstname.lastname@example.org> Reviewed by: Gordon Ross <email@example.com> Reviewed by: Garrett D'Amore <firstname.lastname@example.org> Approved by: Richard Lowe <email@example.com> 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 <firstname.lastname@example.org> Reworked-by: Brian Behlendorf <email@example.com> Closes #955
- Loading branch information...
Showing with 15 additions and 6 deletions.