[LUDOC-31] servicenode is not documented Created: 21/Dec/11 Updated: 27/Nov/12 Resolved: 01/Feb/12 |
|
| Status: | Closed |
| Project: | Lustre Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Richard Henwood (Inactive) | Assignee: | Jessica A. Popp (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Rank (Obsolete): | 7180 |
| Description |
|
--servicenode is not documented in the manual |
| Comments |
| Comment by Richard Henwood (Inactive) [ 21/Dec/11 ] |
|
I have just had a chat with Brian on this topic, the conversation went as follows: B historically, when one formats a target with a failnode and then registers it, the node it was registered from and the fail node are both written as locations for the target. A # mkfs.lustre ... --failnode B /dev/sda
A # mount -t lustre /dev/sda /mnt
with service node you (can) do:
C # mkfs.lustre ... --servicenode A --servicenode B
C # mount -t lustre /dev/sda /mnt
B and nodes A and B will be configured as the nodes that hosts go to for that target |
| Comment by Zhenyu Xu [ 22/Dec/11 ] |
|
manual update tracking at http://review.whamcloud.com/1904 |
| Comment by Richard Henwood (Inactive) [ 22/Dec/11 ] |
|
Excellent! Thanks for getting on this so quickly! |
| Comment by Richard Henwood (Inactive) [ 01/Feb/12 ] |
|
Bobijam's manual update has landed. |