From: Alex Riesen <fork0@users.sf.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: sct@redhat.com, akpm@zip.com.au, adilger@clusterfs.com
Subject: 2.4.20-pre1-ac1: Filesystem panic attempting to mount ext3
Date: Sun, 1 Sep 2002 09:13:27 +0200 [thread overview]
Message-ID: <20020901071327.GA404@steel> (raw)
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.
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.
Sep 1 08:47:32 steel kernel: Found signature1 0x0 signature2 0x0 sector=1.
Sep 1 08:47:32 steel kernel: Directory 1: bad FAT
Sep 1 08:47:32 steel kernel: attempt to access beyond end of device
Sep 1 08:47:32 steel kernel: 16:41: rw=0, want=902238098, limit=3903763
Sep 1 08:47:32 steel kernel: attempt to access beyond end of device
Sep 1 08:47:32 steel kernel: 16:41: rw=0, want=902238099, limit=3903763
Sep 1 08:47:32 steel kernel: attempt to access beyond end of device
Sep 1 08:47:32 steel kernel: 16:41: rw=0, want=902238099, limit=3903763
Sep 1 08:47:32 steel kernel: attempt to access beyond end of device
Sep 1 08:47:32 steel kernel: 16:41: rw=0, want=902238100, limit=3903763
Sep 1 08:47:32 steel kernel: attempt to access beyond end of device
Sep 1 08:47:32 steel kernel: 16:41: rw=0, want=902238100, limit=3903763
Sep 1 08:47:32 steel kernel: attempt to access beyond end of device
Sep 1 08:47:32 steel kernel: 16:41: rw=0, want=902238101, limit=3903763
Sep 1 08:47:32 steel kernel: attempt to access beyond end of device
Sep 1 08:47:32 steel kernel: 16:41: rw=0, want=902238101, limit=3903763
Sep 1 08:47:32 steel kernel: attempt to access beyond end of device
Sep 1 08:47:32 steel kernel: 16:41: rw=0, want=902238102, limit=3903763
Sep 1 08:47:32 steel kernel: Filesystem panic (dev 16:41).
Sep 1 08:47:32 steel kernel: FAT error
Sep 1 08:47:32 steel kernel: File system has been set read-only
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.
# fdisk -l /dev/hdd
Disk /dev/hdd: 255 heads, 63 sectors, 790 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdd1 * 1 486 3903763+ 83 Linux
/dev/hdd2 487 608 979965 83 Linux
/dev/hdd3 609 632 192780 82 Linux swap
/dev/hdd4 633 790 1269135 83 Linux
next reply other threads:[~2002-09-01 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 7:13 Alex Riesen [this message]
2002-09-01 17:02 ` 2.4.20-pre1-ac1: Filesystem panic attempting to mount ext3 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
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=20020901071327.GA404@steel \
--to=fork0@users.sf.net \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox