[LU-7134] Ensure ZFS hostid protection if servicenode/failover options given to mkfs.lustre Created: 10/Sep/15 Updated: 14/Jun/18 Resolved: 31/May/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.9.0 |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Nathaniel Clark | Assignee: | Nathaniel Clark |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | zfs | ||
| Issue Links: |
|
||||||||||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||||||||||
| Description |
|
SPL import protection only exists if hostid is set to a non-zero value. If servicenode or failover is given as an option, then mkfs.lustre should at least warn that hostid is set to zero and import protection won't work. Proposed solution:
|
| Comments |
| Comment by Nathaniel Clark [ 11/Sep/15 ] |
|
SPL supports setting HostID in two ways: option spl spl_hostid to manually specify the HostID to use What if I check the spl hostid /sys/module/spl/parameters/spl_hostid to ensure it's non-zero? It show the HostID is is using (even when read from /etc/hostid) |
| Comment by Gerrit Updater [ 23/Sep/15 ] |
|
Nathaniel Clark (nathaniel.l.clark@intel.com) uploaded a new patch: http://review.whamcloud.com/16611 |
| Comment by Nathaniel Clark [ 07/Dec/15 ] |
|
Upon closer reading of the code in ZFS, I'm not sure enabling this will help in a fail-over scenario or provide adequate protection. The code compares the host's hostid to the one written to the zpool and then prevents import if they don't match (unless one of the hostids is 0). This isn't true multi-mount protection. A more robust solution tracked in issue ZFS #745. |
| Comment by Gerrit Updater [ 31/May/16 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/16611/ |
| Comment by Peter Jones [ 31/May/16 ] |
|
Landed for 2.9 |