[OpenAFS] Advice on using BTRFS for vicep partitions on Linux

Dirk Heinrichs dirk.heinrichs@altum.de
Wed, 22 Mar 2023 16:19:36 +0100


This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------EF60DwiL6MWgGhw4nNlWnehC
Content-Type: multipart/mixed; boundary="------------DDgcm1PK0TPUhVthkUeJyX63";
 protected-headers="v1"
From: Dirk Heinrichs <dirk.heinrichs@altum.de>
To: openafs-info@openafs.org
Message-ID: <bcbd8d97-99a2-206e-f570-8bcb688fcb49@altum.de>
Subject: Re: [OpenAFS] Advice on using BTRFS for vicep partitions on Linux
References: <CA+Tk8fwR5txgR2GJRVi28g8GzcqV-L9jj5OH5UgSy5L+jnM0iQ@mail.gmail.com>
 <d59fd93d-b683-411d-87f6-c5cbdef34f40@spacefrogg.net>
 <CA+Tk8fyQ1bABZxfQ7Qa9aSfF-jAz=-qstceyAYZSP5KTjj2LmQ@mail.gmail.com>
 <da2f42ae-4ad3-1b32-5783-2f22dfb621f4@altum.de>
 <CA+Tk8fzT3dvyYma842BntQ_Pnu_WAegkr9M0f-aFykUcjyfWFw@mail.gmail.com>
In-Reply-To: <CA+Tk8fzT3dvyYma842BntQ_Pnu_WAegkr9M0f-aFykUcjyfWFw@mail.gmail.com>

--------------DDgcm1PK0TPUhVthkUeJyX63
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: base64

Q2lwcmlhbiBDcmFjaXVuOg0KDQo+IFdlbGwsIEkgYmFzZSB0aGlzIHN1cHBvc2l0aW9uIG9u
IG15IHNpbXBsZSBvYnNlcnZhdGlvbiB3aXRoIE9wZW5BRlMncyANCj4gb3duIGNsaWVudCB3
aGljaCBpcyBhbHNvIG91dC1vZi10cmVlIGFuZCByZXF1aXJlcyBjdXN0b20gbW9kdWxlIGJ1
aWxkcyANCj4gKHZpYSBES01TIG9yIGVxdWl2YWxlbnQpLg0KDQo+IEZvciBleGFtcGxlIEkg
dXNlIE9wZW5TVVNFIFR1bWJsZXdlZWQgKHJvbGxpbmcgcmVsZWFzZSksIGFuZCBzb21ldGlt
ZXMgDQo+IEkgbmVlZCB0byBkZWxheSBteSB1cGRhdGVzIHVudGlsIHRoZSBkaXN0cmlidXRp
b24gbWFuYWdlcyB0byBnZXQgdGhlIA0KPiBtb2R1bGVzIHJlYWR5ICh3aXRoIHRoZSBsYXRl
c3QgTGludXgga2VybmVsKS4NCg0KQWgsIE9LLCBJIHNlZS4gWWVhaCwgSSBhbHNvIHNvbWV0
aW1lcyBzZWUgdGhpcyB3aXRoIHRoZSBPcGVuQUZTIG1vZHVsZSANCm9uIERlYmlhbiAqdGVz
dGluZyosIHdoZXJlIGl0IGNhbiBoYXBwZW4gdGhhdCB0aGUga2VybmVsIGlzIHRvbyBuZXcg
c28gDQp0aGF0IHRoZSBtb2R1bGUgZG9lc24ndCBidWlsZCB1bnRpbCBhIGNvbXBhdGliaWx0
eSBmaXggaXMgcmVsZWFzZWQuIEkgDQp1c3VhbGx5IHN3dGljaCB0byB0aGUgaW4ta2VybmVs
IEFGUyBtb2R1bGUgdGVtcG9yYXJpbHkgaW4gdGhlc2UgY2FzZXMuDQoNCkhvd2V2ZXIsIHRo
aXMgbmV2ZXIgaGFwcGVuZWQgb24gRGViaWFuICpzdGFibGUqLCBuZWl0aGVyIGZvciBPcGVu
QUZTLCANCm5vciBmb3IgWkZTLg0KDQpCeWUuLi4NCg0KIMKgwqDCoCBEaXJrDQoNCi0tIA0K
RGlyayBIZWlucmljaHMgPGRpcmsuaGVpbnJpY2hzQGFsdHVtLmRlPg0KTWF0cml4LUFkcmVz
c2U6IEBoZWluaTpjaGF0LmFsdHVtLmRlDQpHUEcgUHVibGljIEtleTogODBGMTU0MEUwM0Ez
OTY4RjNENzlDMzgyODUzQzMyQzQyN0I0ODA0OQ0KUHJpdmFjeSBIYW5kYnVjaDogaHR0cHM6
Ly93d3cucHJpdmFjeS1oYW5kYnVjaC5kZQ0KDQo=

--------------DDgcm1PK0TPUhVthkUeJyX63--

--------------EF60DwiL6MWgGhw4nNlWnehC
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQBbRZ091iOtChJXdXJlzdNRFS0TAUCZBsciQAKCRDJlzdNRFS0
TCJ9AQDFHp558AgAF4PZ6/UpTjNiEjBkhfMumDe4UOXHViQoiwD/cKQTa0cbIX8R
oKl3OBvqX6H3+0yEiwpgAn492UG3LQ8=
=3JXh
-----END PGP SIGNATURE-----

--------------EF60DwiL6MWgGhw4nNlWnehC--