From: "Stephen C. Tweedie" <sct@redhat.com>
To: Alex Riesen <fork0@users.sourceforge.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
sct@redhat.com, akpm@zip.com.au, adilger@clusterfs.com
Subject: Re: 2.4.20-pre1-ac1: Filesystem panic attempting to mount ext3
Date: Mon, 2 Sep 2002 11:38:34 +0100 [thread overview]
Message-ID: <20020902113834.E2507@redhat.com> (raw)
In-Reply-To: <20020901071327.GA404@steel>; from fork0@users.sourceforge.net on Sun, Sep 01, 2002 at 09:13:27AM +0200
Hi,
On Sun, Sep 01, 2002 at 09:13:27AM +0200, Alex Riesen wrote:
> 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.
>
> Than i tried to mount the newly created filesystems and got
> this in syslog:
>
> Sep 1 08:47:32 steel kernel: FAT: Did not find valid FSINFO signature.
Which version of e2fsprogs?
> 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.
mke2fs from older versions of e2fsprogs didn't clear out all the
filesystem and md signatures on a new filesystem.
The right way to avoid this is to tell the kernel to mount the fs as
ext2 or ext3 explicitly, not to rely on the fs-type autodetection in
mount().
Cheers,
Stephen
next prev parent reply other threads:[~2002-09-02 10:34 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
2002-09-01 19:02 ` OGAWA Hirofumi
2002-09-01 19:04 ` Alex Riesen
2002-09-02 10:38 ` Stephen C. Tweedie [this message]
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=20020902113834.E2507@redhat.com \
--to=sct@redhat.com \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=fork0@users.sourceforge.net \
--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.