public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Roland <devzero@web.de>,
	Proxmox VE user list <pve-user@lists.proxmox.com>,
	uwe.sauter.de@gmail.com
Subject: Re: [PVE-User] pve wiki docs wrong -- shared zfs via iscsi isn't possible
Date: Fri, 1 Mar 2024 09:22:57 +0100	[thread overview]
Message-ID: <175ab23a-93d9-450a-b453-81687aef1676@proxmox.com> (raw)
In-Reply-To: <f8439578-5390-452f-8165-9efa6b32e9c1@web.de>

On 3/1/24 09:07, Roland wrote:
> ouch,
> 
> ok, i see "ZFS over iSCSI" is being used as naming in proxmox for that ,
> but it's a little bit misleading
> 
> maybe "iscsi luns hosted on zfs" or "zfs exported iscsi luns" would
> better describe it, but ok, it's like it is now....
> 
> thanks for making it clear.

yes the naming has brought confusion in the past, but we did not
come up with anything better (but not overly long) yet

> 
> btw, can you fix the link to ZFS-over-ISCSI page at the bottom of
> https://pve.proxmox.com/wiki/Storage ? i don't have edit permission there.
> 
> it points to https://pve.proxmox.com/wiki/Legacy:_ZFS_over_iSCSI legacy
> page, whereas that page is now at
> https://pve.proxmox.com/wiki/Legacy:_ZFS_over_ISCSI  (mind it large I in
> ISCSI)

i sent a patch to the devel list, since those pages are autogenerated
from our docs:

https://lists.proxmox.com/pipermail/pve-devel/2024-March/062051.html

regards
Dominik




      parent reply	other threads:[~2024-03-01  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.318.1709233855.434.pve-user@lists.proxmox.com>
2024-02-29 19:24 ` Uwe Sauter
     [not found]   ` <mailman.319.1709241604.434.pve-user@lists.proxmox.com>
2024-03-01  7:36     ` Dominik Csapak
     [not found]       ` <f8439578-5390-452f-8165-9efa6b32e9c1@web.de>
2024-03-01  8:22         ` Dominik Csapak [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=175ab23a-93d9-450a-b453-81687aef1676@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=devzero@web.de \
    --cc=pve-user@lists.proxmox.com \
    --cc=uwe.sauter.de@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal