Re: 2.4.20-pre1-ac1: Filesystem panic attempting to mount ext3

From: OGAWA Hirofumi (hirofumi@mail.parknet.co.jp)
Date: Sun Sep 01 2002 - 14:02:04 EST


Alex Riesen <fork0@users.sf.net> writes:

> 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).

Well, the filesystem is detected by the mount command, except the root
filesystem. And mount command detects FAT before EXT3.

-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sat Sep 07 2002 - 22:00:14 EST