On September 26, 2002 08:42, Theodore Ts'o wrote:
> Hmm... I just tried biult 2.4.19 with the ext3 patch on my UP P3
> machine, using GCC 3.2, and I wasn't able to replicate your problem.
> (This was using Debian's gcc 3.2.1-0pre2 release from testing.)
The whole GCC 3.2 thing was a red herring. Although it ran stable for a few
hours last night (cvs up, compiled a kernel, etc), the filesystem was once
again read-only when I came to check my mail this morning.
The interesting fsck errors this time were:
245782 was part of the orphaned inode list FIXED
245792 was part of the orphaned inode list FIXED
245797...
245782,245792 don't exist according to ncheck.
- -Ryan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9k1tKLGMzRzbJfbQRAj/AAJ9/yPnuSPF3kUTlwFt2wF2JFSJlJwCfc39B
ZKxRtt+hpDHQ7XuiyAYkpNM=
=MHW8
-----END PGP SIGNATURE-----
-
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/