From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Christoph Heiss" <c.heiss@proxmox.com>, <pdm-devel@lists.proxmox.com>
Subject: applied: [PATCH datacenter-manager] docs: local-zfs: fix up hardware raid warning admonition
Date: Mon, 02 Mar 2026 09:46:00 +0100 [thread overview]
Message-ID: <DGS5YCGSNMEY.CIR8G8R3YDQT@proxmox.com> (raw)
In-Reply-To: <20260227160205.1154940-2-c.heiss@proxmox.com>
On Fri Feb 27, 2026 at 5:00 PM CET, Christoph Heiss wrote:
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> Seems this instance was simply overlooked during the recent formatting
> fixes for this section.
>
> docs/local-zfs.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/docs/local-zfs.rst b/docs/local-zfs.rst
> index 9b824cc..170ab9b 100644
> --- a/docs/local-zfs.rst
> +++ b/docs/local-zfs.rst
> @@ -37,9 +37,9 @@ high quality ECC RAM.
> If you use a dedicated cache and/or log disk, you should use an enterprise class SSD (for example,
> Intel SSD DC S3700 Series). This can increase the overall performance significantly.
>
> -IMPORTANT: Do not use ZFS on top of a hardware controller which has its own cache management. ZFS
> -needs to directly communicate with disks. An HBA adapter or something like an LSI controller flashed
> -in ``IT`` mode is recommended.
> +.. IMPORTANT:: Do not use ZFS on top of a hardware controller which has its own cache management. ZFS
> + needs to directly communicate with disks. An HBA adapter or something like an LSI controller flashed
> + in ``IT`` mode is recommended.
>
>
> ZFS Administration
TIL about the word "admonition" :^)
applied, thanks!
prev parent reply other threads:[~2026-03-02 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 16:00 Christoph Heiss
2026-03-02 8:46 ` Lukas Wagner [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=DGS5YCGSNMEY.CIR8G8R3YDQT@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=c.heiss@proxmox.com \
--cc=pdm-devel@lists.proxmox.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