public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Joseph John <jjk.saji@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] HEALTH_ERR , showing x 1 Full osd(s) , guidance requested
Date: Thu, 4 May 2023 11:54:46 +0400	[thread overview]
Message-ID: <CAKeuxjCEXrVjey2UtJfpXjrpJxrZ9KPJON9ObWUQSvtKRircJg@mail.gmail.com> (raw)
In-Reply-To: <mailman.136.1683184866.359.pve-user@lists.proxmox.com>

Dear All
THANKS a lot
Like to update
I managed to add some space, by removing some virtual instances which I was
not using at all. Then we restarted the 4th node which was showing
HEALTH_ERR and now it is working
THANKS A LOT to all who gave advice and support
thanks



On Thu, May 4, 2023 at 11:21 AM Eneko Lacunza via pve-user <
pve-user@lists.proxmox.com> wrote:

>
>
>
> ---------- Forwarded message ----------
> From: Eneko Lacunza <elacunza@binovo.es>
> To: pve-user@lists.proxmox.com
> Cc:
> Bcc:
> Date: Thu, 4 May 2023 09:20:25 +0200
> Subject: Re: [PVE-User] HEALTH_ERR , showing x 1 Full osd(s) , guidance
> requested
> Hi Joseph,
>
> You must resolve that 1 full osd(s) issue. If other OSDs aren't as full,
> you can try to reweight the full OSD so that some info is removed from it.
>
> Another option would be to add additional OSDs.
>
> Cheers
>
> El 4/5/23 a las 8:39, Joseph John escribió:
> > Dear All,
> > Good morning
> > We have a proxmox setup, with 4 nodes, with 6.3-3
> > We   have    Node 1 and Node 2 running with 6.3-3
> > and              Node 3 and Node 4 running with 6.4-15
> >
> > today we noticed that , we were not able to ssh to the virtual instance ,
> > or not able to login using the console based option
> > when I checked the summary, we could see that in "HEALTH_ERR" we are
> > getting message that 1 full osd(s)
> >
> >
> >
> > Thanks
> > Joseph John
> > 00971-50-7451809
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
>
> Eneko Lacunza
> Zuzendari teknikoa | Director técnico
> Binovo IT Human Project
>
> Tel. +34 943 569 206 | https://www.binovo.es
> Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun
>
> https://www.youtube.com/user/CANALBINOVO
> https://www.linkedin.com/company/37269706/
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Eneko Lacunza via pve-user <pve-user@lists.proxmox.com>
> To: pve-user@lists.proxmox.com
> Cc: Eneko Lacunza <elacunza@binovo.es>
> Bcc:
> Date: Thu, 4 May 2023 09:20:25 +0200
> Subject: Re: [PVE-User] HEALTH_ERR , showing x 1 Full osd(s) , guidance
> requested
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>


      parent reply	other threads:[~2023-05-04  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  6:39 Joseph John
2023-05-04  7:29 ` Aaron Lauterer
     [not found] ` <mailman.136.1683184866.359.pve-user@lists.proxmox.com>
2023-05-04  7:54   ` Joseph John [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=CAKeuxjCEXrVjey2UtJfpXjrpJxrZ9KPJON9ObWUQSvtKRircJg@mail.gmail.com \
    --to=jjk.saji@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 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