[lustre-discuss] Lnet not going up with InfiniHost III Lx HCA card

2025-02-06 Thread Ramiro Alba Queipo
Hi all, I am testing Ubuntu 24.04 (6.8.0-52-generic) client with Lustre 2.16.1 over Infiniband and using an old Mellanox DDR card (InfiniHost III Lx HCA). - # ip -br a lo UNKNOWN127.0.0.1/8 ::1/128 eth0 UP 10.2.1.104/16 metric 100 fe80

Re: [lustre-discuss] mkfs.lustre for ZFS draid

2025-02-06 Thread Laura Hild
> But how can I address them when running mkfs.lustre, if I still want to get 7 > OSTs out of it? When we started using draid, we went from having six ten-disk OSTs per OSS to one sixty-disk OST per OSS. I'm unsure why one would want seven OSTs on a single pool, being that if the pool becomes

[lustre-discuss] Lustre and ZFS draid

2025-02-06 Thread Nehring, Shane R [ITS]
Hello All, I didn't want to hijack the other thread today about draid, but I have been meaning to ask questions about it and folks' experience with it in the context of Lustre. Most of my questions come from not having a chance to really play around with draid much. Have you been generally satisf

[lustre-discuss] LUG 2025 REGISTRATION IS NOW OPEN!

2025-02-06 Thread OpenSFS Administration
Hello Lustre Community, We're excited to announce that registration for the Lustre User Group (LUG) 2025 hosted by Stanford University is now open. REGISTER ONLINE. General registration is $499 for early bird registration. Early bird registration closes Feb

Re: [lustre-discuss] mkfs.lustre for ZFS draid

2025-02-06 Thread Cameron Harr
Like Laura, we do one draid pool and one OST per OSS node. Having multiple redundancy groups in the draid doesn't give you multiple block devices; it's still a single pool and device. You could create multiple pools, but then you are perhaps defeating some of the reasons to use draid. On 2/6/2

[lustre-discuss] mkfs.lustre for ZFS draid

2025-02-06 Thread Thomas Roth
Hi all, how are the "redundancy groups" in a ZFS draid specified if you want to format them as Lustre OSTs? I'm used to creating a zpool first, as in `zpool create raidz2 osspool0 */dev/*...`, and then formatting by `mkfs.lustre --ost ... osspool0/ost0` - the OST ost0 will be the only vdev o