mailto:adil...@whamcloud.com>>; Ellis
Wilson mailto:elliswil...@microsoft.com>>;
lustre-discuss@lists.lustre.org<mailto:lustre-discuss@lists.lustre.org>
Subject: [EXTERNAL] Re: [lustre-discuss] Lustre Client Lockup Under Buffered
I/O (2.14/2.15)
You don't often get email from
2022 8:32 AM
> *To:* Andreas Dilger
> *Cc:* lustre-discuss@lists.lustre.org
> *Subject:* Re: [lustre-discuss] Lustre Client Lockup Under Buffered I/O
> (2.14/2.15)
>
>
> Hi Andreas,
>
>
>
> Apologies in advance for the top-post. I’m required to use Outlook for
> wor
tre-discuss@lists.lustre.org
Subject: Re: [lustre-discuss] Lustre Client Lockup Under Buffered I/O
(2.14/2.15)
Hi Andreas,
Apologies in advance for the top-post. I’m required to use Outlook for work,
and it doesn’t handle in-line or bottom-posting well.
Client-side defaults prior to any tun
:54 PM
To: Ellis Wilson
Cc: lustre-discuss@lists.lustre.org
Subject: [EXTERNAL] Re: [lustre-discuss] Lustre Client Lockup Under Buffered
I/O (2.14/2.15)
You don't often get email from
adil...@whamcloud.com<mailto:adil...@whamcloud.com>. Learn why this is
important<http://aka.ms/LearnAboutSende
Hi all,
Recently we've switched from using ZFS to ldiskfs as the backing filesystem to
work around some performance issues and I'm finding that when I put the cluster
under load (with as little as a single client) I can almost completely lockup
the client. SSH (even existing sessions) stall,
