From: "Daniel Aragonés" <danarag@gmail.com>
To: "Cédric Augonnet" <cedric.augonnet@gmail.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Cedric.augonnet@ens-lyon.org
Subject: Re: 2.6.20-mm1 - Oops using Minix 3 file system
Date: Sat, 17 Feb 2007 11:55:17 +0100 [thread overview]
Message-ID: <edd3ff190702170255w1c30fa08v96e5b92baacbd701@mail.gmail.com> (raw)
In-Reply-To: <f56c1ba00702161500x775fe04bl91889b5819cf9ddc@mail.gmail.com>
On 2/17/07, Cédric Augonnet <cedric.augonnet@gmail.com> wrote:
> ...
> Hi Daniel,
>
> On 2.6.20-rc6-mm3 and 2.6.20-mm1, i get an OOPS when using the minix 3
> file system. I enclose the dmesg and the .config to that mail.
>
> Here are the steps to reproduce this oops (they involve using qemu to
> run Minix 3)
> - First create a 2GB image using
> qemu-img create minix.img 2G
> (Please note that this seem to be producing an eroneous image)
> - Then launch Minix inside qemu to make a minix partition on this
> image using mkfs on the corresponding device.
> - Mount the image on loopback using
> mount -t minix -o loop minix.img /mnt/qemu/
> - issue a "df" command on /mnt/qemu
>...
Well, a glance at your dmesg doesn' show that a minix partition was
recognized. Otherwise it would sow it. So you have not such a
partition within your drives.
You are using an emulator to run minix. You will have the same problem
if you run minix2 or minix3 through an emulator and not from a real
minix2 or minix3 partition.
Regards,
Daniel
next prev parent reply other threads:[~2007-02-17 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 23:00 Cédric Augonnet
2007-02-17 10:55 ` Daniel Aragonés [this message]
2007-02-17 13:51 ` Cédric Augonnet
2007-02-17 16:44 ` Daniel Aragonés
2007-02-17 17:53 ` Cédric Augonnet
2007-02-17 18:49 ` Daniel Aragonés
2007-02-17 19:40 ` Bill Davidsen
2007-02-17 20:01 ` Cédric Augonnet
2007-02-18 10:42 ` Cédric Augonnet
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=edd3ff190702170255w1c30fa08v96e5b92baacbd701@mail.gmail.com \
--to=danarag@gmail.com \
--cc=Cedric.augonnet@ens-lyon.org \
--cc=akpm@linux-foundation.org \
--cc=cedric.augonnet@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®