Re: [lustre-discuss] LNet nid down after some thing changed the NICs
Hi Chris, Thanks for your help. I have collected the relevant logs according to your hints. But I need an account to open a ticket on Jira. I have sent an email to the administrator at i...@whamcloud.com. I was wondering if this is the correct way to apply for an account. I only found this email on the site. Regards, Chuanjun Horn, Chris 于2023年2月18日周六 00:52写道： > If deleting and re-adding it restores the status to up then this sounds > like a bug to me. > > > > Can you enable debug tracing, reproduce the issue, and add this > information to a ticket? > > To enable/gather debug: > > # lctl set_param debug=+net > > # lctl dk > /tmp/dk.log > > You can create a ticket at https://jira.whamcloud.com/ > > Please provide the dk.log with the ticket. > > > > Thanks, > > Chris Horn > > > > *From: *lustre-discuss on > behalf of 腐朽银 via lustre-discuss > *Date: *Friday, February 17, 2023 at 2:53 AM > *To: *lustre-discuss@lists.lustre.org > *Subject: *[lustre-discuss] LNet nid down after some thing changed the > NICs > > Hi, > > > > I encountered a problem when using Lustre Client on k8s with kubenet. Very > happy if you could help me. > > > > My LNet configuration is: > > > > net: > - net type: lo > local NI(s): > - nid: 0@lo > status: up > - net type: tcp > local NI(s): > - nid: 10.224.0.5@tcp > status: up > interfaces: > 0: eth0 > > > > It works. But after I deploy or delete a pod on the node. The nid goes > down like: > > > > - nid: 10.224.0.5@tcp > status: down > interfaces: > 0: eth0 > > > > k8s uses veth pairs, so it will add or delete network interfaces when > deploying or deleting pods. But it doesn't touch the eth0 NIC. I can fix it > by deleting the tcp net by `lnetctl net del` and re-add it by `lnetctl net > add`. But I need to do this every time after a pod is scheduled to this > node. > > > > My node OS is Ubuntu 18.04 5.4.0-1101-azure. The Lustre Client is built by > myself from 2.15.1. Is this an expected LNet behavior or I got something > wrong? I re-build and tested it several times and got the same problem. > > > > Regards, > > Chuanjun > ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
Re: [lustre-discuss] ZFS Support For Lustre
Hi, The repos, in general, only work for the kernel they were build for. This will be the supported kernel by the release. Look in the changelog. For 2.15.1: https://wiki.lustre.org/Lustre_2.15.1_Changelog To make newer kernels work you have to compile yourself and that might not even work without patching and hasn't gone through testing. You are better of following the supported kernel on the servers. The client is usually more likely to compile/work on newer kernels, but patching might be needed. Cheers, Hans Henrik On 14.02.2023 13.16, Nick dan via lustre-discuss wrote: Hi I am using Lustre Version 2.15.1 on RedHat 8.8 As mentioned in the link, https://wiki.whamcloud.com/display/PUB/Lustre+Support+Matrix , the ZFS Version required is 2.1.2. However, when I am trying to install ZFS from https://downloads.whamcloud.com/public/lustre/lustre-2.15.1/el8.6/server/RPMS/x86_64/ I am getting the following error [root@st01 user]# yum install https://downloads.whamcloud.com/public/lustre/lustre-2.15.1/el8.6/server/RPMS/x86_64/zfs-2.1.2-1.el8.x86_64.rpm Updating Subscription Management repositories. Last metadata expiration check: 2:01:30 ago on Tue 14 Feb 2023 03:38:48 PM IST. zfs-2.1.2-1.el8.x86_64.rpm 248 kB/s | 649 kB 00:02 Error: Problem: conflicting requests - nothing provides zfs-kmod = 2.1.2 needed by zfs-2.1.2-1.el8.x86_64 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) I have installed the other required packages like libzfs, libzpool, libnvpair, libutil. I am not able to download kmod-zfs version 2.1.2, as the latest version getting downloaded is 2.1.9 Can you help with this or suggest another way to download all supported ZFS Packages? Thanks, Nick Dan ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
Re: [lustre-discuss] Access times for file (file heat)
Anna, there was a client-side file heat mechanism added a few years ago, but I don't know if it is fully functional today. lctl get_param llite.*.*heat* llite.myth-979380fc1800.file_heat=1 llite.myth-979380fc1800.heat_decay_percentage=80 llite.myth-979380fc1800.heat_period_second=60 And then "lfs heat_get " to dump the file heat, it there haven't been any good tools developed yet to list top heat files. Cheers, Andreas > On Feb 7, 2023, at 08:56, Anna Fuchs via lustre-discuss > wrote: > > Hello, > > is there a way to see how many times a file has been accessed ever (like a > heat map)? > > Thanks > Anna > > -- > Anna Fuchs > Universität Hamburg > https://wr.informatik.uni-hamburg.de > > anna.fu...@informatik.uni-hamburg.de > https://wr.informatik.uni-hamburg.de/people/anna_fuchs > > > > ___ > lustre-discuss mailing list > lustre-discuss@lists.lustre.org > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org ___ lustre-discuss mailing list lustre-discuss@lists.lustre.org http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
