public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alistair J Strachan <alistair@devzero.co.uk>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.69-mm9
Date: Sun, 25 May 2003 16:19:40 +0100	[thread overview]
Message-ID: <200305251619.40137.alistair@devzero.co.uk> (raw)

Andrew Morton wrote:
> 
> 
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.69/2.5.69-mm9/
> 
> 
> . 2.5.69-mm9 is not for the timid.  It includes extensive changes to the
>   ext3 filesystem and the JBD layer.  It withstood an hour of testing on
>   my 4-way, but it probably has a couple of holes still.
> 
>   The locking has been finegrained and sleeping locks have been removed -
>   there are now no instances of lock_kernel(), lock_journal() or
>   sleep_on()
>   in JBD or ext3.  ext3 is much quicker on SMP machines.

Hi,

These changes don't even get to login for me. I changed the mm9 command line 
to include init=/bin/sh and got to a prompt. I was able to reproduce an 
enormous number of oopses by issuing:

mount -o remount,rw /

I tried to log it with klogd pointed to a different partition (vfat) but the 
problem segfaults klogd before it commits anything to disc. I'll probably try 
to do it via serial console this evening if nobody else can reproduce this.

Another oddity is that changing my / partition to ext2 in /etc/fstab and 
booting normally (i.e., without init=) doesn't make any difference. If these 
changes are ext3/jbd only, why is my ext3 volume mounted as ext2 still not 
mounting rw?

FWIW, all of my disc's partitions are ext3.

Cheers,
Alistair.

             reply	other threads:[~2003-05-25 15:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25 15:19 Alistair J Strachan [this message]
2003-05-25 20:15 ` 2.5.69-mm9 Andrew Morton
2003-05-25 20:35   ` 2.5.69-mm9 Alistair J Strachan
2003-05-25 20:51     ` 2.5.69-mm9 Mike Fedyk
2003-05-25 20:55     ` 2.5.69-mm9 Andrew Morton
     [not found] <20030525172746.43b9866d.akpm@digeo.com>
     [not found] ` <20030529204324.GF25560@kroah.com>
2003-05-29 23:48   ` 2.5.69-mm9 Alistair J Strachan
  -- strict thread matches above, loose matches on Subject: below --
2003-05-25 11:27 2.5.69-mm9 Andrew Morton
2003-05-25 12:56 ` 2.5.69-mm9 Rudmer van Dijk
2003-05-25 14:07   ` 2.5.69-mm9 Ed Sweetman
2003-05-25 20:06     ` 2.5.69-mm9 Andrew Morton
2003-05-25 20:29       ` 2.5.69-mm9 Adrian Bunk
2003-05-25 16:47   ` 2.5.69-mm9 Nicholas Wourms
2003-05-25 17:06 ` 2.5.69-mm9 Adam Kropelin
2003-05-25 21:56 ` 2.5.69-mm9 Felipe Alfaro Solana
2003-05-25 22:48   ` 2.5.69-mm9 Andrew Morton
2003-05-25 23:16     ` 2.5.69-mm9 Neil Brown
2003-05-25 23:19     ` 2.5.69-mm9 Trond Myklebust

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=200305251619.40137.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --cc=akpm@digeo.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