all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Yannis Milios <yannis.milios@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] LVM over ISCSI issue
Date: Wed, 12 Aug 2020 10:51:47 +0100	[thread overview]
Message-ID: <CAFiF2OrWGEmv4xH4RkUVAiAXKf4brT_3id2YHmvK_Reht+nwAQ@mail.gmail.com> (raw)
In-Reply-To: <mailman.7.1597219945.464.pve-user@lists.proxmox.com>

The fact that it was successful at least once with the discard option
disabled is a progress in my opinion. Did you ever have a successful clone
job with discard enabled ?

Also, the error seems to be different in each case...

with discard enabled:
qemu-img: error while writing at byte 1990201344:* Input/output error*

with discard disabled: qemu-img: error while writing at byte
2147483136: *Device
or resource busy*

Can you check also in dmesg for any clues during each case ?
Also, when was the last time this was working without issues ? any changes
both on PVE and NAS side after that ?

Y.


On Wed, 12 Aug 2020 at 09:12, Amin Vakil via pve-user <
pve-user@lists.proxmox.com> wrote:

>
>
>
> ---------- Forwarded message ----------
> From: Amin Vakil <info@aminvakil.com>
> To: pve-user@lists.proxmox.com
> Cc:
> Bcc:
> Date: Wed, 12 Aug 2020 12:42:10 +0430
> Subject: [PVE-User] LVM over ISCSI issue
> No difference, totally random.
>
> Also here are the logs of clones in case I'm missing something.
>
> Error, discard enabled: http://ix.io/2tXB
> OK, discard disabled: http://ix.io/2tXC
> Error, discard disabled: http://ix.io/2tXD
>
> > Just out of curiosity, can you temporarily disable discard support on
> > the
> > target VM disk to see if that will make a difference?
>
>
>
>
> ---------- Forwarded message ----------
> From: Amin Vakil via pve-user <pve-user@lists.proxmox.com>
> To: pve-user@lists.proxmox.com
> Cc: Amin Vakil <info@aminvakil.com>
> Bcc:
> Date: Wed, 12 Aug 2020 12:42:10 +0430
> Subject: [PVE-User] LVM over ISCSI issue
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>


       reply	other threads:[~2020-08-12  9:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
     [not found] <mailman.12.1597237532.464.pve-user@lists.proxmox.com>
2020-08-12 13:26 ` Yannis Milios
     [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] <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=CAFiF2OrWGEmv4xH4RkUVAiAXKf4brT_3id2YHmvK_Reht+nwAQ@mail.gmail.com \
    --to=yannis.milios@gmail.com \
    --cc=pve-user@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal