Derek Su
Derek Su
cc @shuo-wu @innobead
@DamiaSan Please update the pipeline status of the issue.
@innobead Can I pick up the ticket?
Making the ticket more general such as `[DOC] Expected inconsistent behavior of between v1 and v2 volume` would be appreciated. cc @yangchiu
> @derekbit is this a duplicated one as you have worked on another issue related to unmap? There is a subtask https://github.com/longhorn/longhorn/issues/7925.
@Kampadais improved the v1 data path based on my previous PoC. https://github.com/longhorn/longhorn-engine/pull/1067 I think we can work on the improvement in v1.8.0 together and replace the iSCSI frontend with the...
> Agree that we can implement it in 1.8.0. Because I am working on v1 performance related topics, I can help to drive this ticket if it is ok Derek...
@CaptainKrby It looks the share manager is still wating for the volume. Can you check if there is any clue in the longhorn-manager logs?
> I'm experiencing the same issue. One of my pods is stuck in the **Init:4/5** state. Upon describing the pod, I received the following details: > > ``` > MountVolume.MountDevice...
> same issue, it suddenly stopped working. Obviously something happened but I cannot tell what ! My cluster uses ubuntu 22.04 and mixed kernel: > > ```shell > Linux oci-autour.****...