public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>, dea <dea@corep.it>
Subject: Re: [pbs-devel] Possible problem on NFS storage with release 2-3-3 (??)
Date: Tue, 14 Mar 2023 09:20:14 +0100	[thread overview]
Message-ID: <d18c1576-0eba-ee9c-281b-9b7e23ce1c89@proxmox.com> (raw)
In-Reply-To: <37b93c67-fbae-3736-26a2-9ff3af7dc4fd@corep.it>

Hi,

Am 09/03/2023 um 13:38 schrieb dea:
> Downgrade via dpkg from 2.3-3 to 2.3-2 (and change kernel to 6.1) and works very fast, as usually.
> 

what packages where in the "bad" update set? Can you please check /var/log/apt/history.log ?

> I don't know if the problem is in the kernel or in the 2.3-3 package, but this way it works as it should.
> 

Hmm, we moved proxmox-backup-server version 2.3.3-1 to no-subscription over a month
ago (2023-02-10) and had not seen any wide-spreading reports of general problems
introduced by that version.

So if a new kernel was pulled in too it could be indeed related to that.
The used Hardware (CPU, NIC, ...) would be good to know too, maybe it's a regression
specific to some component of your system.


> The system is in production, so I can't do too many tests and reboots...
> 
> I was exasperated by the slowness, so I made two changes at once (I know that diagnostically it's the worst solution, but not having time or a way to give too much disruption I couldn't do one test at a time).

It'd be really great if you could find some time to test 2.3.3-1 again while keeping
the newer 6.1 kernel booted. Downgrading that back again shouldn't require that much
time (at least less than switching kernel), and would help to tell if PBS itself can
be excluded from the regression hunt.

 - thomas




  reply	other threads:[~2023-03-14  8:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  8:52 dea
2023-03-09 12:38 ` dea
2023-03-14  8:20   ` Thomas Lamprecht [this message]
2023-03-14  8:45     ` dea
2023-03-15  7:51       ` dea
2023-04-13 14:16       ` dea
2023-03-14 12:30     ` dea

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=d18c1576-0eba-ee9c-281b-9b7e23ce1c89@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=dea@corep.it \
    --cc=pbs-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal