On September 28, 2002 07:18, Theodore Ts'o wrote:
> Oh, one other thing. I'm pretty sure the rest of the errors you saw
> were a result of the fact that you had your filesystem set to remount
> the filesystem read-only after running into errors. When the error
> was detected, all existing updates to the filesystem are aborted (to
> minimize damage to the filesystem), and that can leave the filesystem
> in a somewhat inconsistent state, although nothing which e2fsck
> shouldn't be able to fix.
The loopback filesystem was set to continue on errors. The only things fsck
noticed were the short directory entries and unattached inodes. It actually
tried to connect lost+found to lost+found, BTW ;)
- -Ryan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9li6yLGMzRzbJfbQRAtn2AKCUoXTYKuVMkfB17wd4RWua0YtTmgCfV+Uh
Gg//dy/RviPA5LWvpfDYQAw=
=lno1
-----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/