From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] change grub_print_error to use stderr for the utils
Date: Sun, 17 Aug 2008 18:37:33 +0200 [thread overview]
Message-ID: <20080817163733.GB10862@thorin> (raw)
In-Reply-To: <1218988023.4080.31.camel@fz.local>
On Sun, Aug 17, 2008 at 05:47:03PM +0200, Felix Zielcke wrote:
> Am Sonntag, den 17.08.2008, 17:34 +0200 schrieb Robert Millan:
> > Hiding errors is a very bad practice. And hiding them because the output
> > is ugly or because something is reporting false positives is even worse
> > IMHO.
> >
> > This "out of disk" sounds like a false positive indeed. It's a bug,
> > somewhere. Something is handling errors in a place where this particular
> > error shouldn't be reported. Maybe it should handle them somewhere else,
> > or maybe they should be handled selectively.
>
> This is because of my nForce 4 Hardware RAID 0 (i.e. dmraid).
> Linux sees 2 disks (sda,sdb) and the partition table of the first is for
> the 2 disks combined.
> Both disk have only 80 GB but both combined have 160 GB.
If I understood correctly, nvidia's is a _software_ RAID solution which is
implemented in Linux, in BIOS and in Windows (via non-native drivers), and
is marketed as if it were hardware RAID.
Anyway, this doesn't answer the question on where is this "out of disk"
error issued, and why.
> Oh I should have said in my case.
> The BIOS presents GRUB only one (hd0) for the combined 2 disks.
Ah, I see. Sounds like a very nasty situation. We'll probably need special
logic at install time to sort this out? At least, just to skip raid.mod
inclussion and use UUIDs for the rest.
Anyway, how is this related to the "out of disk" error?
> This doestn't look that good either ;)
>
> [...]
> error: out of disk
> Installation finished. No error reported.
This "No error reported" seems to assume non-critical errors aren't
possible. How about we remove that part of the message?
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-08-17 16:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 15:30 [PATCH] change grub_print_error to use stderr for the utils Felix Zielcke
2008-08-12 15:35 ` Felix Zielcke
2008-08-12 15:36 ` Vesa Jääskeläinen
2008-08-12 15:43 ` Felix Zielcke
2008-08-12 15:41 ` Robert Millan
2008-08-12 15:52 ` Felix Zielcke
2008-08-13 9:37 ` Marco Gerards
2008-08-12 16:54 ` Felix Zielcke
2008-08-13 9:38 ` Marco Gerards
2008-08-13 17:35 ` [RFC] " Felix Zielcke
2008-08-13 18:41 ` Marco Gerards
2008-08-13 19:14 ` Felix Zielcke
2008-08-14 7:07 ` Marco Gerards
2008-08-14 7:39 ` Felix Zielcke
2008-08-14 8:03 ` Marco Gerards
2008-08-14 8:05 ` Felix Zielcke
2008-08-14 17:54 ` Robert Millan
2008-08-14 18:57 ` Felix Zielcke
2008-08-16 15:06 ` Felix Zielcke
2008-08-17 15:07 ` Robert Millan
2008-08-17 15:24 ` Felix Zielcke
2008-08-17 15:34 ` Robert Millan
2008-08-17 15:47 ` Felix Zielcke
2008-08-17 16:37 ` Robert Millan [this message]
2008-08-17 16:58 ` Felix Zielcke
2008-08-17 17:04 ` Bean
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=20080817163733.GB10862@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/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.