linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Cumming <ryan@completely.kicks-ass.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] Add ext3 indexed directory (htree) support
Date: Thu, 26 Sep 2002 15:53:02 -0700	[thread overview]
Message-ID: <200209261553.07593.ryan@completely.kicks-ass.org> (raw)
In-Reply-To: <20020926220432.GB10551@think.thunk.org>

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

  reply	other threads:[~2002-09-26 22:47 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 20:03 tytso
2002-09-25 20:34 ` Andreas Dilger
2002-09-25 20:41 ` Dave Jones
2002-09-25 21:08   ` Andreas Dilger
2002-09-25 21:34   ` Theodore Ts'o
2002-09-25 22:54 ` Jeff Garzik
2002-09-25 23:29   ` Theodore Ts'o
2002-09-25 23:45     ` Ryan Cumming
2002-09-26  3:27       ` Theodore Ts'o
2002-09-26  5:23         ` Ryan Cumming
2002-09-26  5:57           ` Theodore Ts'o
2002-09-26  6:22             ` Ryan Cumming
2002-09-26 14:05               ` Theodore Ts'o
2002-09-26  6:25             ` Ryan Cumming
2002-09-26 11:25               ` Daniel Egger
2002-09-26  7:41             ` Ryan Cumming
2002-09-26 13:23               ` Theodore Ts'o
2002-09-26 15:42               ` Theodore Ts'o
2002-09-26 19:08                 ` Ryan Cumming
2002-09-26 19:51                   ` Horst von Brand
2002-09-26 19:59                     ` Ryan Cumming
2002-09-26 22:04                   ` Theodore Ts'o
2002-09-26 22:53                     ` Ryan Cumming [this message]
2002-09-26 23:57                       ` Theodore Ts'o
2002-09-27  1:00                         ` Ryan Cumming
2002-09-27  3:24                           ` Theodore Ts'o
2002-09-27  4:12                         ` Andreas Dilger
2002-09-27  7:55                           ` Ryan Cumming
2002-09-28  1:20                           ` Ryan Cumming
2002-09-28  1:46                             ` Ryan Cumming
2002-09-28 14:13                             ` Theodore Ts'o
2002-09-28 14:18                               ` Theodore Ts'o
2002-09-28 22:35                                 ` Ryan Cumming
2002-09-28 17:27                               ` [Ext2-devel] " Andreas Dilger
2002-09-28 18:43                                 ` chrisl
2002-09-28 19:45                                 ` chrisl
2002-09-28 22:30                               ` Ryan Cumming
2002-09-29  7:03                               ` [PATCH] fix htree dir corrupt after fsck -fD chrisl
2002-09-29  8:16                                 ` Ryan Cumming
2002-09-29  8:36                                   ` Ryan Cumming
2002-09-30  2:46                                   ` Ryan Cumming
2002-09-29 14:13                                 ` Theodore Ts'o
2002-09-25 23:31 ` [BK PATCH] Add ext3 indexed directory (htree) support Daniel Egger
2002-09-26  0:32   ` Randy.Dunlap
2002-09-26  0:50 ` Aaron Lehmann
2002-09-26  3:28   ` Theodore Ts'o
2002-10-02  9:11 tytso

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=200209261553.07593.ryan@completely.kicks-ass.org \
    --to=ryan@completely.kicks-ass.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --subject='Re: [BK PATCH] Add ext3 indexed directory (htree) support' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).