I knew an lfsck would identify the orphaned objects. That’s great that it will
move those objects to an area we can triage. With ownership still intact (and
I assume time stamps too), I think this will be helpful for at least some of
the users to recover some of their data. Thanks Andreas.
I
In the absence of backups, you could try LFSCK to link all of the orphan OST
objects into .lustre/lost+found (see lctl-lfsck_start.8 man page for details).
The data is still in the objects, and they should have UID/GID/PRJID assigned
(if used) but they have no filenames. It would be up to you t
The first yes toon to ask is what is your end goal? If you just want to build
only a client that is mounting to an existing server, then you can disable the
server functionality:
./configure --disable-server
and it should build fine.
If you want to also build a server, and *really* want i
My system: Debian 11, kernel version 5.10.0-13-amd64; I have the
following source code:
# ll /usr/src/
total 117916
drwxr-xr-x 2 root root 4096 Aug 21 09:19 linux-config-5.10/
drwxr-xr-x 4 root root 4096 Jul 25 2022
linux-headers-5.10.0-12-amd64/
drwxr-xr-x 4 root root 4096 J
