Re: [lustre-discuss] 2.10 <-> 2.12 interoperability?

2019-05-03 Thread Hans Henrik Happe
On 03/05/2019 22.41, Andreas Dilger wrote: > On May 3, 2019, at 14:33, Patrick Farrell wrote: >> >> Thomas, >> >> As a general rule, Lustre only supports mixing versions on servers for >> rolling upgrades. >> >> - Patrick > > And only then between maintenance versions of the same release (e.g.

Re: [lustre-discuss] 2.10 <-> 2.12 interoperability?

2019-05-03 Thread Andreas Dilger
On May 3, 2019, at 14:33, Patrick Farrell wrote: > > Thomas, > > As a general rule, Lustre only supports mixing versions on servers for > rolling upgrades. > > - Patrick And only then between maintenance versions of the same release (e.g. 2.10.6 and 2.10.7). If you are upgrading, say,

Re: [lustre-discuss] 2.10 <-> 2.12 interoperability?

2019-05-03 Thread Patrick Farrell
Thomas, As a general rule, Lustre only supports mixing versions on servers for rolling upgrades. - Patrick From: lustre-discuss on behalf of Thomas Roth Sent: Wednesday, April 24, 2019 3:54:09 AM To: lustre-discuss@lists.lustre.org Subject:

Re: [lustre-discuss] lfs find

2019-05-03 Thread Nathaniel Clark
That would mean the union of `lfs find --pool HDD /mnt/lustre` and `lfs find ! --pool HDD /mnt/lustre` would NOT be ALL files.  I agree a semantic for finding files that are have no elements in a pool would be useful, I think using a not operator where it's not the inverse would be surprising.