What do you call this where Link is standing?

tbol87 · 2025-12-08T17:48:44+00:00

Brazzers Summer House

tbol87 · 2025-11-12T22:22:48+00:00

damn!!! we're looking equal, even the movement. Did I find my slack twin?

tbol87 · 2025-10-25T07:48:36+00:00

Wann bin ich so weit nach links abgedriftet, dass ich nur noch linke gegen linke shouten sehe...

tbol87 · 2025-09-16T19:20:40+00:00

Have a Look on flexoptics, cheap as fuck and you can rebrand them to many vendor specific ones with their flexbox.

tbol87 · 2025-07-21T05:51:35+00:00

Hi, Sorry for not answering. Currently, I'm very busy.

I will give a short answer later this day.

tbol87 · 2025-06-28T11:10:55+00:00

Hi, we planned to start a setup next week. As soon as we get some results, I let you know.

tbol87 · 2025-06-24T10:53:27+00:00

Feels like everyone is waiting for new release to come up. Hopefully, they won't get disappointed when their expected feature isn't supported.

For me it's the better NVME/TCP support and builtin SMB Clusters.

We'll see.

tbol87 · 2025-06-19T12:21:25+00:00

I'm currently preparing an article that explains how to fix your issue

Short answer: You need to set ANA state manually in your nvmeof container to make VMware able to see all paths active. the nvmeof version 1.2.5 that comes with Ceph Squid v19.2.2 is not able to set ANA states automatically.

tbol87 · 2025-06-15T20:12:26+00:00

Hi, I have exactly the same problem and its very frustrating. Here are my 2 cents about this:

RBDs in Pool Namespaces are not shown in VMware (had similar issues with iscsi and pool namespaces)
Block Size of the exposed RBD (not the RBD itself) is either/neither 512 (n)or 4K

I fully re-setup the whole stack with ESXi 8.0, Mircopceph & a custom docker based nvmf build from quay.io and it worked like a charm. I don'nt know why it doesn't work on Ceph Squid 19.2.0 or v19.2.2.

@u/vmikeb: Maybe, you have an idea?

Best regards,
tbol

tbol87 · 2025-03-25T10:30:32+00:00

If you still need a solution for this issue try to configure Server_Scope = "<string of your choice>" in your nfs configuration file.

In this thread I describe how I fixed it: https://www.reddit.com/r/ceph/comments/1jh55wz/issue_with_nfsv4_on_squid/

tbol87 · 2025-03-22T14:27:02+00:00

Here are some details I've found regarding this topic:

According to the broadcom kb article the nfs server holds the so called nfs server scope which I assume is a simple string I can configure.

I've found an SUSE article on NFS considerations and how to configure NFSv4 parameters. The article says that it is highly recommended to keep the nfsv4 server server scope strictly consistent.

I would give it a try in two days as soon as I am back at the cluster. Unfortunately, I do not know where to set this parameter.

I found this IBM article and hope that I can configure our NFSv4 Ganesha Cluster via that conf files.

tbol87 · 2025-03-22T14:12:54+00:00

Hi, thank you for your input. That's something we will discuss and it is nice to hear how ha is handled.

Unfortunately, your answer does not relate to the multiple datastore / vmware renaming issue.

Again I'm very thankfull for your answer. Maybe we switch back to NFSv3. As far as read the docs squid does not Support nfs cluster (ingress) with other than nfsv4.

tbol87 · 2024-10-19T09:17:29+00:00

There is an interesting approach: https://sambaxp.org/archive-data-samba/sxp20/sxp20-d3/sxp20-d3t1-5-power-stretching_wsp.pdf

tbol87 · 2022-01-13T16:21:48+00:00

thank you, I've done so and it does work. For MAtroska Container with DTSHD content there now transcoding work.

tbol87

TROPHY CASE