All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <fork0@users.sf.net>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20-pre1-ac1: Filesystem panic attempting to mount ext3
Date: Sun, 1 Sep 2002 19:30:36 +0200	[thread overview]
Message-ID: <20020901173036.GA20418@steel> (raw)
In-Reply-To: <87k7m5hccc.fsf@devron.myhome.or.jp>

OGAWA Hirofumi, Sun, Sep 01, 2002 19:02:59 +0200:
> Alex Riesen <fork0@users.sf.net> writes:
> 
> > Hello,
> > 
> > the problem appeared on the first partition of an ide
> > IBM-DHEA-36481 with one fat partition on it. I repartioned
> > the device (4 primaries) and "mke2fs -j" three of them.
> 
> [...]
> 
> > 
> > Umount produced something as well:
> > 
> > Sep  1 08:47:54 steel kernel: FAT: Did not find valid FSINFO signature.
> > Sep  1 08:47:54 steel kernel: Found signature1 0x0 signature2 0x0 sector=1.
> > 
> > Assuming that some garbage was left on the disk event after mke2fs,
> > i did "dd if=/dev/zero of=/dev/hdd1 bs=512", which cured the problem,
> > after being followed by mke2fs.
> 
> It's problem of fatfs, and I think it's fixed in 2.5 series. I'll try
> to back porting the part of fatfs of 2.5 series.

Thanks.
Does mounting somehow depend on order of initialization of filesystems?
The fatfs is a module here, and it was inserted last (ext3 is compiled in).

-alex

  reply	other threads:[~2002-09-01 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-01  7:13 2.4.20-pre1-ac1: Filesystem panic attempting to mount ext3 Alex Riesen
2002-09-01 17:02 ` OGAWA Hirofumi
2002-09-01 17:30   ` Alex Riesen [this message]
2002-09-01 19:02     ` OGAWA Hirofumi
2002-09-01 19:04       ` Alex Riesen
2002-09-02 10:38 ` Stephen C. Tweedie
2002-09-02 10:42   ` Alex Riesen

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=20020901173036.GA20418@steel \
    --to=fork0@users.sf.net \
    --cc=hirofumi@mail.parknet.co.jp \
    --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 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.