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 21:35:36 +0100	[thread overview]
Message-ID: <200305252135.37109.alistair@devzero.co.uk> (raw)
In-Reply-To: <20030525131512.45ce0cc2.akpm@digeo.com>

[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]

On Sunday 25 May 2003 21:15, you wrote:
>
> Changing fstab will not cause / to be mounted by ext2: the kernel makes the
> decision for /.  You may be able to use "rootfstype=" (I don't think I've
> ever tried it).
>
> The proper way to convert to ext2 is:
>
> - boot with init=/bin/sh
>
> - /sbin/tune2fs -O ^has_journal /dev/hda1
>
> - /sbin/e2fsck -fy /dev/hda1
>
> - reboot, edit /etc/fstab for the non-root filesystems.

Thanks for this info. I just removed the journal and now have / mounted 
permanently as ext2. -mm9 got to login without a problem. I deliberately kept 
my /home volume as ext3 but commented it out in /etc/fstab.

I logged in as root and did:

mount -t ext3 /dev/discs/disc0/part3 /home

This also worked fine, I could read all the files on the volume. However, when 
I did:

touch /home/tmp
sync

The kernel barfed out the attached junk and the file was never committed. The 
volume was not corrupted as I was able to reboot with -mm6 and all is fine. 
tmp does not exist on the volume.

Presumably this is of more help to you. Since / is now ext2, I'm unencumbered 
and so will be able to test anything you like.

Cheers,
Alistair.

[-- Attachment #2: oopses.gz --]
[-- Type: application/x-gzip, Size: 2089 bytes --]

  reply	other threads:[~2003-05-25 20:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25 15:19 2.5.69-mm9 Alistair J Strachan
2003-05-25 20:15 ` 2.5.69-mm9 Andrew Morton
2003-05-25 20:35   ` Alistair J Strachan [this message]
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=200305252135.37109.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