Re: [lustre-devel] RFC: Spill device for Lustre OSD

Andreas Dilger via lustre-devel <[email protected]> Tue, 4 Nov 2025 17:46:43 -0700
Newsgroups org.lustre.lists.lustre-devel
Message-ID <[email protected]>
--===============5975551429210522294==
Content-Type: multipart/signed;
 boundary="Apple-Mail=_15B6F48A-53CC-4BDC-8EFD-7DF39AEA8412";
 protocol="application/pgp-signature"; micalg=pgp-sha256


--Apple-Mail=_15B6F48A-53CC-4BDC-8EFD-7DF39AEA8412
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Nov 4, 2025, at 5:28 PM, Jinshan Xiong <[email protected]> wrote:
> On Tue, Nov 4, 2025 at 4:20=E2=80=AFPM Andreas Dilger wrote:
>> I don't see how the layout xattr format is related to =
filesystem-level
>> scanning?  This is "just" the xattr format *STORED ON THE OST =
OBJECT*,
>> and it could be handled by direct device-level (OST) scan tools as =
well.
>=20
> I see. I initially thought you proposed the spill device would =
function as a mirror and that the existing software stack would handle =
it.
>=20
> Are we going to store the spilled object's status in the layout? It =
sounds difficult because you will have to initiate a layout change from =
the OSTs. I think we still need to store such an xattr locally in the =
OST object.

I'm exactly proposing that the layout xattr be stored on the OST object.
It would have the same format as the existing Lustre layout stored on
the MDT, but *maybe* a different name (e.g. "trusted.spl", =
"trusted.osd",
or whatever).

I'm not sure if using "trusted.lov" will confuse filesystem scanning
tools or help them...  It probably makes sense to have a different
xattr name, just in case we want MDT spilling (e.g. NVRAM->QLC) in
the future.

>> This would allow mirrors (FLR), multiple spill devices (multiple FLR
>> mirrors), concatenated devices (PFL), etc.  It just avoids adding new
>> formats that need to be parsed, printed, etc.

Cheers, Andreas






--Apple-Mail=_15B6F48A-53CC-4BDC-8EFD-7DF39AEA8412
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIzBAEBCAAdFiEEDb73u6ZejP5ZMprvcqXauRfMH+AFAmkKnnQACgkQcqXauRfM
H+DAmA//XcaDBRhzNmwwozpOOIZh1F0BLJHdLnapYos71PiJolKEbmedU2DwNxF0
Es5ORpWJOyLuZ1QMk5THHsZwPr28Glgg19Dm3Q3MuY9x9v8nUZ38lCl83aoOdX45
kTcEMZadqaLlsyrts+zCOzRpB4gs8/omGTkEw0Pw/MHWrCM/JnuuwhGXE1uk1KHU
/KRlZReV6fzMuhoVAXEUULJFdpNtVVbaO1jUlG5Y00+NiNPGYrd9WVO2RAr1vUnZ
TBX9RjZ4GGSlsYDng3lKKR0mqizGQWzbjSq9m6O7Fzl14TH+Lkwi06BitOS213lx
eBvyRmAWQUp4zrr8ZqwwTNDTLDcnQdl3WZEc25THLWcT9983sZuQVYnKFn5cZkjz
gJdKUzoj1zZ7SYj2p0IxEgMKqzwfvR/VUDvX31VjdDScnzFB8lIgo4rQzhonCa0w
ZC/y5CpzlOPOa1yzd8aK8pPSXh6+L35HzE0I02BJo2eNSQQB2YQyhJj0yFJFgFe9
JYGXMkpOvpeVsotFKLH7cGtB/LOuJSNaXLovV4cuQ9MssWQDIkYiQMKMjdfo+EQ4
pvAR8ISCpZNxtk5ahq/iCxCK9NMebdWdO/xIP3wC++OV/IRN0uxudGJ8BVwkbCmx
kujKcsH0bnOrw4FDqrZZe80VPnSPH8CSxL2JUYOtL5RCdEGLQ8w=
=qjvQ
-----END PGP SIGNATURE-----

--Apple-Mail=_15B6F48A-53CC-4BDC-8EFD-7DF39AEA8412--

--===============5975551429210522294==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
lustre-devel mailing list
[email protected]
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org

--===============5975551429210522294==--