From: Yusuf Hadiwinata <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Support <[email protected]>,
Ammar Rafli Arkan <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Paber Panjaitan <[email protected]>
Subject: Re: [## 385523 ##] Disk I/O di Neo Lite kembali bermasalah
Date: Fri, 12 Jul 2024 13:31:30 +0000 [thread overview]
Message-ID: <KL1PR06MB6670FFDFA7777985250C25A7B6A62@KL1PR06MB6670.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <ZpEt76/[email protected]>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
Thnks you
Mau memastikan, apakah sebelum terjadi Blocking Thread ada OOM
thnks
________________________________
From: Ammar Faizi <[email protected]>
Sent: Friday, 12 July 2024 20:21
To: Yusuf Hadiwinata <[email protected]>
Cc: Support <[email protected]>; Ammar Rafli Arkan <[email protected]>; Alviro Iskandar Setiawan <[email protected]>; GNU/Weeb Mailing List <[email protected]>; Paber Panjaitan <[email protected]>
Subject: Re: [## 385523 ##] Disk I/O di Neo Lite kembali bermasalah
On Fri, Jul 12, 2024 at 01:20:29PM +0000, Yusuf Hadiwinata wrote:
> Untuk IP 103.175.218.159 boleh di infokan OS dan Kernel Version yang di gunakan
root@wjv001:~/fio# curl ip.me
103.175.218.159
root@wjv001:~/fio# uname -r
6.8.1-af-server-2024-03-19-g760d1c206de8
root@wjv001:~/fio# cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"
PRETTY_NAME="Ubuntu 22.04.4 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
root@wjv001:~/fio#
--
Ammar Faizi
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
[-- Attachment #2: Type: text/html, Size: 3953 bytes --]
next prev parent reply other threads:[~2024-07-12 13:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 11:12 Disk I/O di Neo Lite kembali bermasalah Ammar Faizi
2024-07-12 11:27 ` Re:[## 385523 ##] " Ammar Rafli
2024-07-12 11:34 ` [## " Ammar Faizi
2024-07-12 11:40 ` Ammar Rafli
2024-07-12 11:47 ` [## " Ammar Faizi
2024-07-12 11:57 ` Ammar Rafli
2024-07-12 12:09 ` [## " Ammar Faizi
2024-07-12 12:20 ` Ammar Rafli
2024-07-12 12:23 ` Ammar Rafli
2024-07-12 12:42 ` [## " Ammar Faizi
2024-07-12 13:00 ` Ammar Rafli
2024-07-12 13:19 ` [## " Ammar Faizi
2024-07-12 13:06 ` Yusuf Hadiwinata
2024-07-12 13:12 ` Yusuf Hadiwinata
2024-07-12 13:13 ` Ammar Faizi
2024-07-12 13:20 ` Yusuf Hadiwinata
2024-07-12 13:21 ` Ammar Faizi
2024-07-12 13:31 ` Yusuf Hadiwinata [this message]
2024-07-12 13:40 ` Ammar Faizi
2024-07-12 14:12 ` Ammar Rafli
2024-07-12 14:45 ` [## " Yusuf Hadiwinata
2024-07-12 13:12 ` Ammar Faizi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=KL1PR06MB6670FFDFA7777985250C25A7B6A62@KL1PR06MB6670.apcprd06.prod.outlook.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox