Chuck Fouts

Thanks, for the update!

Hi @appropriate-jan, @lopf, and @AndreasDeCrinis, This issue has been fixed with the Trident v23.01.0 release. Changes were made to improve Trident's iSCSI volume attachment code to deal with multiple scenarios...

Closing this issue as the excess IOPS was being generated by the Prometheus configuration. Thank you @jbuchanan360 for posting a comment on your investigation.

Closing this issue as a response to the request for additional information wasn't provided. This issue can be reopened if it is determined that a problem exists related to the...

This issue was fixed with [commit 9b78a23](https://github.com/NetApp-openstack-dev/trident/commit/9b78a23f968b478f51c95283224f2e478a0f9b96) and is included in the Trident v22.10 release.

Hi @chaudhariatul, Docker doesn't officially support expanding a volume via that CLI. The `docker volume create` command only supports creating the volume. As a work around, you can [expand your...

Hi @thomasmeeus, We've talked to ONTAP about this issue previously. There isn't actually a set percentage that we can increase the volume by where you wouldn't still run into this...

@rikgig, it sounds like you are using a "retain" reclaim policy so that the volume doesn't get deleted. Trident maintains a CR (tvol) to keep track of this volume in...

Hi @StrangeBubble, FC support is evaluated periodically. As was mentioned previously, it is best to work with your account team to escalate feature requests like FC support.

@travisghansen thanks for doing the research on this. ONTAP blocks are 4KB in size so overriding this to always be 4096 for ext4 and ext3 would be ideal. It isn't...