From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub-probe seems to be having problems
Date: Thu, 08 Mar 2012 18:46:42 +0100 [thread overview]
Message-ID: <4F58F082.1090504@gmail.com> (raw)
In-Reply-To: <20120305200729.GE14853@caffeine.csclub.uwaterloo.ca>
On 05.03.2012 21:07, Lennart Sorensen wrote:
> On Sat, Mar 03, 2012 at 11:00:28PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>> On 01.03.2012 20:47, Lennart Sorensen wrote:
>>> root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md1 --target=partmap
>>> /usr/sbin/grub-probe: error: disk `mduuid/dc00bd3a0e9491bb0b66fa8b9246c2e8' not found.
>> Attached patch eliminates some idiosyncracies problems with mdraid
>> 1.x. Also fixes partial import problem and raid5 partial array
>> problem.
> No improvement that I can see.
>
> Is it possible there is endianess bugs in the code?
Yes, I've just fixed one. grub-fstest works on big-endian now. Couldn't
test grub-probe since the Ubuntu on my PPC test machine is outdated.
> 1.x format is ALWAYS little endian, but I am on a big endian machine.
> 0.9 format is host endianess.
GRUB always assumes that RAID metadata is in little-endian. We don't
have any "native-endian parsers" since we assume that grub-probe results
are valid for GRUB runtime as well even if they run on different
endianness. If we need any support for structures which can be either le
or be we compile code twice, once for le, once for be (look at e.g. cpio
code). I couldn't test the images created on big-endian platform due to
ancient distro.
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-03-08 17:47 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 19:47 grub-probe seems to be having problems Lennart Sorensen
2012-03-01 20:04 ` Lennart Sorensen
2012-03-01 20:07 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-01 20:15 ` Lennart Sorensen
2012-03-01 20:19 ` Lennart Sorensen
2012-03-03 22:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 20:07 ` Lennart Sorensen
2012-03-05 23:10 ` Lennart Sorensen
2012-03-08 17:46 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-03-08 19:01 ` Lennart Sorensen
2012-03-08 19:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 20:15 ` Lennart Sorensen
2012-03-08 23:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-09 14:53 ` Lennart Sorensen
2012-03-09 0:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-09 15:39 ` Lennart Sorensen
2012-03-09 15:43 ` Lennart Sorensen
2012-03-09 15:47 ` Lennart Sorensen
2012-03-09 15:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
[not found] ` <20120309160538.GA14853@caffeine.csclub.uwaterloo.ca>
2012-03-09 18:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-09 18:39 ` Lennart Sorensen
2012-03-09 20:37 ` Lennart Sorensen
2012-03-19 21:28 ` Lennart Sorensen
2012-03-20 10:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-20 19:02 ` Lennart Sorensen
2012-03-20 19:10 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-20 19:13 ` Lennart Sorensen
2012-03-20 19:14 ` Lennart Sorensen
2012-03-20 19:41 ` Lennart Sorensen
2012-03-20 19:11 ` Lennart Sorensen
2012-03-22 2:27 ` Fwd: " jlcenter
2012-03-22 2:46 ` NeilBrown
2012-03-22 17:52 ` Fwd: " jlcenter
2012-03-09 0:24 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4F58F082.1090504@gmail.com \
--to=phcoder@gmail.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.