Re: [lustre-discuss] Odd behavior with tunefs.lustre and device index

2024-01-25 Thread Backer via lustre-discuss
Thank you Andreas. Are you aware of any paid engagements/support for requests like these to get changes done quickly? On Wed, 24 Jan 2024 at 20:52, Andreas Dilger wrote: > This is more like a bug report and should be filed in Jira. > That said, no guarantee that someone would be able to > work

Re: [lustre-discuss] Odd behavior with tunefs.lustre and device index

2024-01-24 Thread Andreas Dilger via lustre-discuss
This is more like a bug report and should be filed in Jira. That said, no guarantee that someone would be able to work on this in a timely manner. On Jan 24, 2024, at 09:47, Backer via lustre-discuss mailto:lustre-discuss@lists.lustre.org>> wrote: Just pushing it on to the top of inbox :) Or

Re: [lustre-discuss] Odd behavior with tunefs.lustre and device index

2024-01-24 Thread Backer via lustre-discuss
Just pushing it on to the top of inbox :) Or is there any other distribution list that is more appropriate for this type of questions? I am also trying devel mailing list. On Sun, 21 Jan 2024 at 18:34, Backer wrote: > Just to clarify. OSS-2 is completely powered off (hard power off without >

Re: [lustre-discuss] Odd behavior with tunefs.lustre and device index

2024-01-21 Thread Backer via lustre-discuss
Just to clarify. OSS-2 is completely powered off (hard power off without any graceful shutdown) before start working on OSS-3. On Sun, 21 Jan 2024 at 12:12, Backer wrote: > Hi All, > > I am seeing a behavior with tunefs.lustre. After changing the failover > node and trying to mount an OST,

[lustre-discuss] Odd behavior with tunefs.lustre and device index

2024-01-21 Thread Backer via lustre-discuss
Hi All, I am seeing a behavior with tunefs.lustre. After changing the failover node and trying to mount an OST, getting getting the following error: The target service's index is already in use. (/dev/sdd) After the above error, and performing --writeconf once, I can repeat these steps (see