From: Sven Luther <sven.luther@wanadoo.fr>
To: Andrew Morton <akpm@osdl.org>,
Mary Edie Meredith <maryedie@osdl.org>,
piggin@cyberone.com.au, linux-kernel@vger.kernel.org,
jenny@osdl.org
Subject: Re: Nick's scheduler v18
Date: Fri, 14 Nov 2003 11:34:03 +0100 [thread overview]
Message-ID: <20031114103403.GA5177@iliana> (raw)
In-Reply-To: <20031113222751.GJ2014@mis-mike-wstn.matchmail.com>
On Thu, Nov 13, 2003 at 02:27:51PM -0800, Mike Fedyk wrote:
> On Thu, Nov 13, 2003 at 11:39:06AM -0800, Andrew Morton wrote:
> > What filesystem was being used?
> >
> > If it was ext2 then perhaps you hit the recently-fixed block allocator
> > race. That fix was merged after test9. Please check the kernel logs for
> > any filesystem error messages.
> >
> > Also, please retry the run, see if it is repeatable.
>
> Did that hit ext3 also? ISTR, getting some "access beyond end of device"
> while running ext3.
BTW, i did encounter some problem with amiga partitions which had some
bad values due to a bug in libparted now fixed. The head size was
counted double or something such, which resulted in accesses beyon the
end of the device. It has a funny effect though. The box would freeze,
and the IDE led would flash in 1 second intervals. Not sure it is the
expected behavior. This is with a 2.4.22 kernel, both on x86 and ppc.
Friendly,
Sven Luther
next prev parent reply other threads:[~2003-11-14 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 17:20 Nick's scheduler v18 Nick Piggin
2003-11-13 18:07 ` Mary Edie Meredith
2003-11-13 19:39 ` Andrew Morton
2003-11-13 22:27 ` Mike Fedyk
2003-11-14 10:34 ` Sven Luther [this message]
2003-11-14 5:45 ` Nick Piggin
2003-11-13 21:30 ` Martin J. Bligh
2003-11-14 2:12 ` Nick Piggin
[not found] <1068589319.1557.1.camel@localhost.localdomain>
2003-11-11 22:30 ` Tom Sightler
2003-11-12 0:38 ` Nick Piggin
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=20031114103403.GA5177@iliana \
--to=sven.luther@wanadoo.fr \
--cc=akpm@osdl.org \
--cc=jenny@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maryedie@osdl.org \
--cc=piggin@cyberone.com.au \
/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;
as well as URLs for NNTP newsgroup(s).