Need sanity check on reconfiguring ZIL

Status
Not open for further replies.

taupehat

Explorer
Joined
Dec 20, 2016
Messages
54
Right now "zpool status" is griping about non-native block size for the logs device. Here's the bit that matters:
Code:
  logs
  mirror-5  ONLINE  0  0  0
  gpt/log0  ONLINE  0  0  0  block size: 512B configured, 4096B native
  gpt/log1  ONLINE  0  0  0  block size: 512B configured, 4096B native

As I understand it, the right solution is to delete and recreate mirror-5 with the correct block size. From what I've seen this is safe so long as the zpool version is higher than 15, zpool upgrade -v returns "This system supports ZFS pool feature flags." and no version number. Which of the feature flags do I need to see enabled in order to safely remove and replace the ZIL?

Any further tips or warnings greatly appreciated.
 

m0nkey_

MVP
Joined
Oct 27, 2015
Messages
2,739
Did you use the CLI to create the mirror? If so, that's the problem. Destroy the mirror and re-create it using the GUI.
 

Arwen

MVP
Joined
May 17, 2014
Messages
3,611
Yes. It is safe to destroy the SLOG mirror.

Any pool with feature flags begins at legacy version 28.
Thus, greater than the pool version 15 required.
 
Status
Not open for further replies.
Top