All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daris Nevil <Daris.Nevil@snmc.com>
To: Steve Rossi <srossi@ccrl.mot.com>
Cc: Embedded Linux PPC List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: e2fsck?
Date: Wed, 17 May 2000 09:32:31 -0500	[thread overview]
Message-ID: <3922AD7F.7618E190@snmc.com> (raw)
In-Reply-To: 3922A729.F5A922FE@ccrl.mot.com


Steve,

I may be getting mixed up with another utility, but I think that e2fsck
requires the /proc filesystem to be mounted.  You can do this by:

    mount -p proc /proc /proc

Give that a try and let us know if that solves the problem.

Daris Nevil
SiSIC Inc/Simple Network Magic Corporation
www.snmc.com

Steve Rossi wrote:

> Has anyone successfully compiled e2fsck for 8xx? I was able to compile
> it and run it, but it seg faults with the following output:
>
> sh-2.03# e2fsck /dev/sda2
> e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> /dev/sda2 contains a file system with errors, check forced.
> Pass 1: Checking inodes, blocks, and sizes
> Segmentation fault
>
> TIA,
> Steve
>
> --
> -------------------------------------------------------
> Steven K. Rossi                     srossi@ccrl.mot.com
> Staff Engineer
> Multimedia Communications Research Laboratory
> Motorola Labs
> -------------------------------------------------------
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-17 14:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-17 14:05 e2fsck? Steve Rossi
2000-05-17 14:32 ` Daris Nevil [this message]
2000-05-17 14:58   ` e2fsck? Steve Rossi
2000-05-17 15:04 ` e2fsck? Marcus Sundberg
2000-05-17 15:18   ` e2fsck? Daris Nevil
2000-05-17 15:35     ` e2fsck? Marcus Sundberg
2000-05-17 15:57       ` e2fsck? Steve Rossi
2000-05-18  8:21         ` e2fsck? Marcus Sundberg
2000-05-18 16:15           ` e2fsck? Daris Nevil

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=3922AD7F.7618E190@snmc.com \
    --to=daris.nevil@snmc.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=srossi@ccrl.mot.com \
    /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.