Re: [lustre-discuss] [EXTERNAL] Re: Lustre Client Lockup Under Buffered I/O (2.14/2.15)

Thanks for facilitating a login for me Peter. The bug with all logs and info I could think to include has been opened here: https://jira.whamcloud.com/browse/LU-15468 I'm going to keep digging on my end, but if anybody has any other bright ideas or experiments they'd like me to try, don't

Re: [lustre-discuss] [EXTERNAL] Re: Lustre Client Lockup Under Buffered I/O (2.14/2.15)

Ellis JIRA accounts can be requested from i...@whamcloud.com Peter From: lustre-discuss on behalf of Ellis Wilson via lustre-discuss Reply-To: Ellis Wilson Date: Thursday, January 20, 2022 at 6:20 AM To: Raj , Patrick Farrell Cc:

Re: [lustre-discuss] [EXTERNAL] Re: Lustre Client Lockup Under Buffered I/O (2.14/2.15)

Thanks Raj - I've checked all of the nodes in the cluster and they all have peer_credits set to 8, and credits are set to 256. AFAIK that's quite low - 8 concurrent sends to any given peer at a time. Since I only have two OSSes, for this client, that's only 16 concurrent sends at a given

Re: [lustre-discuss] Lustre Client Lockup Under Buffered I/O (2.14/2.15)

Ellis, I would also check the peer_credit between server and the client. They should be same. On Wed, Jan 19, 2022 at 9:27 AM Patrick Farrell via lustre-discuss < lustre-discuss@lists.lustre.org> wrote: > Ellis, > > As you may have guessed, that function just set looks like a node which is >

[lustre-discuss] Lustre 2.12.6 client crashes

Date: Thu, 20 Jan 2022 12:07:40 + From: Christopher Mountford To: lustre-discuss@lists.lustre.org Subject: Client crashes User-Agent: NeoMutt/20170306 (1.8.0) Hi All, We've started getting some fairly regular client panics on out lustre 2.12.7 filesystem, looking at the stack trace I think