Liang Zheng
Liang Zheng
I tried to create a loop device on the local node, it is normal. In addition, I found a very strange phenomenon, if I only create pvc, and then do...
> Did you supply mkfs options that Ceph CSI hard-codes: `-m0 -Enodiscard,lazy_itable_init=1,lazy_journal_init=1` when trying with a loop device? Yes, I followed your commands and it's normal like below. @idryomov ```...
I created a rbd image throug k8s PVC, then map and mount it. It's normal to do like this. ``` [root@k1 ~]# rbd ls -p pool-51312494-44b2-43bc-8ba1-9c4f5eda3287 csi-vol-da7f0cdc-4a3a-11ed-8ab9-3a534777138b [root@k1 ~]# lsblk...
This problem can be stably reproduced when pvc is applied in pods. ``` 🍺 /root/go/src/deeproute.ai/smd ☞ git:(pool) rbd map pool-51312494-44b2-43bc-8ba1-9c4f5eda3287/csi-vol-8a32112e-4a3e-11ed-8ab9-3a534777138b /dev/rbd0 🍺 /root/go/src/deeproute.ai/smd ☞ git:(pool) lsblk -f NAME FSTYPE LABEL...
Thanks for your advice and help @idryomov @Madhu-1
Hi @Madhu-1 , you could disable ext4 journal option after creating pods. 1. create pvc and pod 2. delete pod, because `e2fsck` should make sure the disk is not used....
Because `jbd2` process caused the high IO, I want to disable ext4 journal to optimize it. 
Thank you for your investigation. I have two environments that can be reproduced stably. I am not sure if it is related to the system. @Madhu-1 ``` [root@node01 smd]# uname...
I have meet same issue. @jkatz ``` ➜ /root/go/src/github.com/CrunchyData/postgres-operator-examples ☞ git:(main) ✗ kubectl logs -n postgres-operator hippo-instance1-6cpp-0 postgres-startup Initializing ... ::postgres-operator: uid::26 ::postgres-operator: gid::26 65534 ::postgres-operator: postgres path::/usr/pgsql-13/bin/postgres ::postgres-operator: postgres...