public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Oguz Bektas <o.bektas@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH storage 1/2] smartctl: remove to-be-replaced disk_tests
Date: Mon, 10 May 2021 14:27:00 +0200	[thread overview]
Message-ID: <20210510122700.GA9727@gaia.proxmox.com> (raw)
In-Reply-To: <c187e887-de27-10c2-0115-f0b36b95b7c3@proxmox.com>

On Mon, May 10, 2021 at 02:15:37PM +0200, Dominik Csapak wrote:
> hi,
> 
> sorry for the long wait on a review, but better
> late than never ;)
> 
> so one high level comments:
> 
> why do you remove all disk tests ??
> they did not only test the smart output, but also the
> usage, ssd/hdd detection, vendor/model etc...
> 
> i understand that you do not have the original disks
> for the smartctl -j output, but it should not be
> *that* hard to fake it ;)

at the time i couldn't figure out a way to keep all the tests working
while also adding the json changes, so for proof of concept i went for
the simpler option.

thomas thought it would also be acceptable to incrementally
add the new tests over time, making sure that everything works with the
new changes.

i have to admit i haven't really tried to fake the outputs, mainly
because there were a lot of disk types that produce different kind of
results (one issue stefan noticed at an earlier version was that his
disk's smart result returned an array with the temperature sensors,
while the disks i've tested did not have these.)

all these vendor-specific quirks make it really hard to produce reliable
tests without the real hardware.

> 
> and even if it is, please change the tests so that
> only the smart part is not tested anymore, e.g. with a flag
> in the test itself....

that can be an option, indeed
> 
> so please find a way to keep the tests (as much as you can)
> 
> i'll comment more on the second patch
> 
> 




      reply	other threads:[~2021-05-10 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 13:40 Oguz Bektas
2021-04-01 13:40 ` [pve-devel] [PATCH storage 2/2] smartctl: use json parsing Oguz Bektas
2021-04-01 14:24 ` [pve-devel] [PATCH v2 " Oguz Bektas
2021-05-10 12:21   ` Dominik Csapak
2021-05-10 12:35     ` Oguz Bektas
2021-05-10 12:15 ` [pve-devel] [PATCH storage 1/2] smartctl: remove to-be-replaced disk_tests Dominik Csapak
2021-05-10 12:27   ` Oguz Bektas [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=20210510122700.GA9727@gaia.proxmox.com \
    --to=o.bektas@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pve-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