Derek Su

After checking the expansion flow, `v.Spec.Size` is the nominal size of a volume `v.Status.ActualSize` is the total size of the snapshot files and volume head. `e.Spec.Size` is also the nominal...

I list the following cases  From the cases, if we send the `e.Spec.Size` and `e.Status.CurrentSize` to engine, then we can figure out the crashed replicas from the two values...

> @derekbit May I have question about case 7. It seems that this is the case in which replica successfully expanded but the engine crashed. In this case, how do...

e2e https://ci.longhorn.io/job/private/job/longhorn-tests-regression/2023/

As the benchmarking result, if the volume and the single replica are on the same node, the latency and iops can be improved significantly.  In addition, the tcp can...

Replace the tcp connection between the engine and the single replica with unix-domain-socket. - The IOPS and Latency are improved. - The bandwidth number is saturated, so the improvement is...

@patsys Could you please elaborate more the reason and the purpose of the feature request?

The verbosities of longhorn-manager and the components dynamically deployed during start up are set to 2 now. The log level (2) is better choice for logging useful information and avoiding...

Yeah, it's typo. Thanks for the correctness. Current log level is `debug`. Some log messages should be set to `trace` to avoid the message flood.

@rlex , what's your k3s version?