On Jan 19, 2024, at 13:48, Pavlo Khmel via lustre-discuss
mailto:lustre-discuss@lists.lustre.org>> wrote:
Hi,
I'm trying to remove 4 OSTs.
# lfs osts
OBDS:
0: cluster-OST_UUID ACTIVE
1: cluster-OST0001_UUID ACTIVE
2: cluster-OST0002_UUID ACTIVE
3: cluster-OST0003_UUID ACTIVE
. . .
I
Dear Andreas, All,
Thanks for your response. Just to give you some more information. Yes, we have
run e2fsck on all OSTs, MDTs, and MGS and all come back completely clean. We
have also removed and recreated the quota files on them, again without any
issues. The underlying storage upon which
Hi,
I'm trying to remove 4 OSTs.
# lfs osts
OBDS:
0: cluster-OST_UUID ACTIVE
1: cluster-OST0001_UUID ACTIVE
2: cluster-OST0002_UUID ACTIVE
3: cluster-OST0003_UUID ACTIVE
. . .
I moved all files to other OSTs. "lfs find" cannot find any files on these 4
OSTs.
# time lfs find --ost 0 --ost
For the lustre-client-dkms, maybe you can --skip-broken to force it to
install, and it will automatically compile the source code of it, during
which you can check the error message. Use dkms command or go directly to
the source folder there to check. If there's no error message there, then
you
It looks like there may be a couple of test tools that are referencing python2,
but it definitely isn't needed
for normal operation. Are you using the lustre-client binary or the
lustre-client-dkms? Only one is needed.
For the short term it would be possible to override this dependency, but
Hi,
FYI
It seems that lustre-client-dkms-2.15.4 is still checking for python2 and does
not install on AlmaLinux 9.3
# dnf --enablerepo=lustre-client install lustre-client lustre-client-dkms
Last metadata expiration check: 0:04:50 ago on Fri Jan 19 11:43:54 2024.
Error:
Problem: conflicting
