From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Container exceed disk size
Date: Thu, 28 Oct 2021 10:34:49 +0200 [thread overview]
Message-ID: <dcf265b4-123d-c150-6fe4-89cf46b70bb2@proxmox.com> (raw)
In-Reply-To: <7cc6faa3-6129-8d52-72cd-4b86419ce432@marcobertorello.it>
Am 28.10.21 um 10:10 schrieb Bertorello, Marco:
> Il 28/10/2021 10:02, Fabian Ebner ha scritto:
>> Am 27.10.21 um 10:03 schrieb Bertorello, Marco:
>>> Il 27/10/2021 09:55, Fabian Ebner ha scritto:
>>>>
>>>> I'm not able to reproduce the issue here. Could you share the output of
>>>> zpool history | grep subvol-119
>>>> ?
>>>
>>> sure, the output is in the attached file.
>>>
>>
>> Thanks! So the container was migrated to another node and then
>> replicated/migrated back. But in our code, the -p flag is used for zfs
>> send, so properties like refquota should be preserved. Could you also
>> check the history on the other node(s)?
>
> Yes, all containers have replica to other nodes (4 nodes cluster). This
> specific container was migrated just one time (as far as I remember) to
> another node and back.
>
> As attachment, the history on the other node.
>
Unfortunately, the log is as expected and I still wasn't able to
reproduce the issue. Let's hope it was a one-time event, but if it
happens again (and even better if you manage to get a reproducer) feel
free to report it to us and/or upstream ZFS.
> Best regards,
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2021-10-28 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 9:42 Bertorello, Marco
2021-10-27 7:13 ` Fabian Ebner
2021-10-27 7:31 ` Bertorello, Marco
2021-10-27 7:55 ` Fabian Ebner
2021-10-27 8:03 ` Bertorello, Marco
2021-10-28 8:02 ` Fabian Ebner
2021-10-28 8:10 ` Bertorello, Marco
2021-10-28 8:34 ` Fabian Ebner [this message]
2021-10-28 8:44 ` Bertorello, Marco
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=dcf265b4-123d-c150-6fe4-89cf46b70bb2@proxmox.com \
--to=f.ebner@proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox