Re: [BK PATCH] Add ext3 indexed directory (htree) support

Ryan Cumming
2002-09-26T22:47:52Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On September 26, 2002 15:04, Theodore Ts'o wrote:
> Was there anything in the logs at all? There should be, if the
> filesystem was remounted read-only.
There is nothing. grep -i "ext3" /var/log/messages returned a whole lot of the
usual:
Sep 25 15:51:00 completely kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Sep 25 15:51:00 completely kernel: EXT3 FS 2.4-0.9.18, 14 May 2002 on
ide0(3,2), internal journal
The one mildly interesting thing was:
Sep 26 11:49:06 (none) kernel: EXT3-fs: INFO: recovery required on readonly
filesystem.
Sep 26 11:49:06 (none) kernel: EXT3-fs: write access will be enabled during
recovery.
Sep 26 11:49:06 (none) kernel: EXT3-fs warning (device ide0(3,2)):
ext3_clear_journal_err: Filesystem error recorded from previous mount: IO
failure
Sep 26 11:49:06 (none) kernel: EXT3-fs warning (device ide0(3,2)):
ext3_clear_journal_err: Marking fs in need of filesystem check.
Sep 26 11:49:06 (none) kernel: EXT3-fs: ide0(3,2): orphan cleanup on readonly
fs
Sep 26 11:49:06 (none) kernel: EXT3-fs: recovery complete.
Sep 26 11:49:06 (none) kernel: EXT3-fs: mounted filesystem with ordered data
mode.
Sep 26 11:49:06 (none) kernel: EXT3 FS 2.4-0.9.18, 14 May 2002 on ide0(3,2),
internal journal

> The real question is what was the original error that caused the ext3
> filesystme to decide it needed to remount the filesystem read-only.
> That should be in your logs, since calls to ext3_error should always
> cause printk's explaining what the error was to be sent to the logs.
I've seen the printk's (although I didn't write down this one). However, they
are never hitting the disk. I could try to log the messages to my FreeBSD
mail server...

> The filesystem wouldn't happen to be running close to full either on
> the number of blocks or the number of inodes, would it?
Inode count: 4767744
Block count: 9522528
Reserved block count: 476126
Free blocks: 2362117
Free inodes: 4490071

Seems to be fine.....

- -Ryan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)

iD8DBQE9k4/TLGMzRzbJfbQRAgp6AJ9Xp7WviFP9ByQaUJ8Ak9sYVf1C4ACffemS
tS4gB+W4WE7VrPKa+tan/68=
=MhXA
-----END PGP SIGNATURE-----