Re: [lustre-discuss] servicenode /failnode
You're totally correct! De : lustre-discuss au nom de Sid Young via lustre-discuss Répondre à : Sid Young Date : vendredi 26 février 2021 à 00:45 À : lustre-discuss Objet : [EXTERNAL] [lustre-discuss] servicenode /failnode CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. G'Day all, I'm rebuilding my Lustre cluster again and in doing so I am trying to understand the role of the --servicenode option when creating an OST. There is an example in the doco shown as this: [root@rh7z-oss1 system]# mkfs.lustre --ost \ > --fsname demo \ > --index 0 \ > --mgsnode 192.168.227.11@tcp1 \ > --mgsnode 192.168.227.12@tcp1 \ > --servicenode 192.168.227.21@tcp1 \ > --servicenode 192.168.227.22@tcp1 \ > /dev/dm-3 But its not clear what the service node actually is. Am I correct in saying the service nodes are the IP's of the two OSS servers that can manage this particular OST (the HA pair)? Sid Young ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
[lustre-discuss] servicenode /failnode
G'Day all, I'm rebuilding my Lustre cluster again and in doing so I am trying to understand the role of the --servicenode option when creating an OST. There is an example in the doco shown as this: [root@rh7z-oss1 system]# mkfs.lustre --ost \ > --fsname demo \ > --index 0 \ > --mgsnode 192.168.227.11@tcp1 \ > --mgsnode 192.168.227.12@tcp1 \ > --servicenode 192.168.227.21@tcp1 \ > --servicenode 192.168.227.22@tcp1 \ > /dev/dm-3 But its not clear what the service node actually is. Am I correct in saying the service nodes are the IP's of the two OSS servers that can manage this particular OST (the HA pair)? Sid Young ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
[Lustre-discuss] servicenode/failnode and comma separated values
All, I notice there seems to be a difference between putting all your nids as comma separated values for servicenode/failnode and putting them as separate entries for each one. Here is an output of a dryrun against an OST that was created using multiple --servicenode= options. I ran tune2fs with the same nids, but as comma separated on a single --servicenode option: snip== #tunefs.lustre --dryrun --servicenode=10.100.1.10@o2ib,10.100.1.11@o2ib,10.100.1.12@o2ib,10.100.1.13@o2ib,10.100.1.14@o2ib,10.100.1.15@o2ib --verbose /dev/VG_Hamming/WORK_OST17checking for existing Lustre data: found Reading CONFIGS/mountdata Read previous values: Target: WORK-OST0011 Index: 17 Lustre FS: WORK Mount type: ldiskfs Flags: 0x1062 (OST first_time update no_primnode ) Persistent mount opts: errors=remount-ro Parameters: mgsnode=10.100.1.11@o2ib:10.100.1.10@o2ib failover.node=10.100.1.10@o2ib failover.node=10.100.1.11@o2ib failover.node=10.100.1.12@o2ib failover.node=10.100.1.13@o2ib failover.node=10.100.1.14@o2ib failover.node=10.100.1.15@o2ib Permanent disk data: Target: WORK:OST0011 Index: 17 Lustre FS: WORK Mount type: ldiskfs Flags: 0x1062 (OST first_time update no_primnode ) Persistent mount opts: errors=remount-ro Parameters: mgsnode=10.100.1.11@o2ib:10.100.1.10@o2ib failover.node=10.100.1.10@o2ib failover.node=10.100.1.11@o2ib failover.node=10.100.1.12@o2ib failover.node=10.100.1.13@o2ib failover.node=10.100.1.14@o2ib failover.node=10.100.1.15@o2ib failover.node=10.100.1.10@o2ib,10.100.1.11@o2ib,10.100.1.12@o2ib,10.100.1.13@o2ib,10.100.1.14@o2ib,10.100.1.15@o2ib exiting before disk write. snip== So is there a difference in how lustre will use those failover.node settings? If so, what is it and if not, shouldn't there be some consistency in how that is stored/displayed? Brian Andrus ITACS/Research Computing Naval Postgraduate School Monterey, California voice: 831-656-6238 ___ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
