All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robbie Harwood <rharwood@redhat.com>
To: Michael Chang via Grub-devel <grub-devel@gnu.org>,
	The development of GNU GRUB <grub-devel@gnu.org>
Cc: Michael Chang <mchang@suse.com>,
	meghanaprakash@in.ibm.com, avnish@linux.vnet.ibm.com,
	brking@linux.vnet.ibm.com, mamatha4@linux.vnet.ibm.com,
	mchauras@linux.vnet.ibm.com
Subject: Re: [PATCH] ieee1275/ofdisk: retry on open and read failure
Date: Tue, 28 Mar 2023 12:08:54 -0400	[thread overview]
Message-ID: <jlgzg7w97u1.fsf@redhat.com> (raw)
In-Reply-To: <20230328083456.rxspg42vvmdfp6lh@lore>

[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]

Michael Chang via Grub-devel <grub-devel@gnu.org> writes:

> On Tue, Mar 28, 2023 at 11:00:01AM +0530, Mukesh Kumar Chaurasiya wrote:
>> Sometimes, when booting from a very busy SAN, the access to the
>> disk can fail and then grub will eventually drop to grub prompt.
>> This scenario is more frequent when deploying many machines at
>> the same time using the same SAN.
>> This patch aims to force the ofdisk module to retry the open or
>> read function after it fails. We use MAX_RETRIES to specify the
>> amount of times it will try to access the disk before it
>> definitely fails.
>
> To clarify this is a continuation of previous patch [1]. Obviously the
> count of retries, MAX_RETRIES, has been replaced by a timeout,
> RETRY_DEFAULT_TIMEOUT, which is 15000 milliseconds or fifteen seconds.
> It appears that the description was not updated accordingly and needs to
> be amended.
>
> [1] https://www.mail-archive.com/grub-devel@gnu.org/msg32174.html

We carry that ^ patch basically as-is downstream.  This proposed patch
seems rather different: there's environment logic, more functions, etc..
As Michael says, it would be helpful if what's happening here could be
clarified - especially since the description mentions MAX_RETRIES from
Diego's patch, but there's no mention of Diego's authorship in the
commit message, and no MAX_RETRIES in the code...

Be well,
--Robbie

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2023-03-28 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  5:30 [PATCH] ieee1275/ofdisk: retry on open and read failure Mukesh Kumar Chaurasiya
2023-03-28  8:34 ` Michael Chang
2023-03-28 16:08   ` Robbie Harwood [this message]
2023-03-29  5:30   ` [PATCH V2] " Mukesh Kumar Chaurasiya
2023-04-05 16:41     ` Daniel Kiper
  -- strict thread matches above, loose matches on Subject: below --
2021-05-07 14:15 [PATCH] " Diego Domingos

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=jlgzg7w97u1.fsf@redhat.com \
    --to=rharwood@redhat.com \
    --cc=avnish@linux.vnet.ibm.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=grub-devel@gnu.org \
    --cc=mamatha4@linux.vnet.ibm.com \
    --cc=mchang@suse.com \
    --cc=mchauras@linux.vnet.ibm.com \
    --cc=meghanaprakash@in.ibm.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.