From: Yannis Milios <yannis.milios@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: proxmoxve <pve-user@pve.proxmox.com>, Amin Vakil <info@aminvakil.com>
Subject: Re: [PVE-User] LVM over ISCSI issue
Date: Wed, 12 Aug 2020 14:26:45 +0100 [thread overview]
Message-ID: <CAFiF2Oq14DnbL56YvVuPxm=vw-bjM445Zyf9NHvo_gwK7US_BA@mail.gmail.com> (raw)
In-Reply-To: <mailman.12.1597237532.464.pve-user@lists.proxmox.com>
On Wed, 12 Aug 2020 at 14:05, Amin Vakil via pve-user <
pve-user@lists.proxmox.com> wrote:
>
> There isn't any useful log on qnap NAS, but most of times its RAM is
> full and it doesn't have any cache. Maybe qnap prevents writing when
> it's fully used and maybe proxmox thinks it has complete access over
> /dev/sdb and therefore when it sees it cannot write gives an
> input/output error.
>
Indeed, that would make sense...
> Isn't there a tweak in proxmox to retry writing on iscsi until it succeeds?
>
I cannot comment on that, as I'm not using iscsi on pve. You can check in
pve documentation or wiki, otherwise on open-iscsi documentation.
Y.
next parent reply other threads:[~2020-08-12 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.12.1597237532.464.pve-user@lists.proxmox.com>
2020-08-12 13:26 ` Yannis Milios [this message]
[not found] <mailman.3.1597226401.1866.pve-user@lists.proxmox.com>
[not found] ` <mailman.8.1597230763.464.pve-user@lists.proxmox.com>
2020-08-12 12:51 ` Yannis Milios
[not found] <5f048801-ccb1-18ec-bdaa-86b8425ea9ae@aminvakil.com>
[not found] ` <mailman.7.1597219945.464.pve-user@lists.proxmox.com>
2020-08-12 9:51 ` Yannis Milios
[not found] <ff746f5b-4b13-4f04-4fd1-434a79c61658@aminvakil.com>
[not found] ` <mailman.733.1597143132.12071.pve-user@lists.proxmox.com>
2020-08-11 16:19 ` Yannis Milios
[not found] <mailman.721.1597132770.12071.pve-user@lists.proxmox.com>
2020-08-11 8:25 ` Yannis Milios
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='CAFiF2Oq14DnbL56YvVuPxm=vw-bjM445Zyf9NHvo_gwK7US_BA@mail.gmail.com' \
--to=yannis.milios@gmail.com \
--cc=info@aminvakil.com \
--cc=pve-user@lists.proxmox.com \
--cc=pve-user@pve.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