From: Oleg Drokin <green@namesys.com>
To: Herbie Hopkins <Herbie@Hopkins.net>
Cc: Hans Reiser <reiser@namesys.com>, Reiserfs <reiserfs-list@namesys.com>
Subject: Re: slow mount
Date: Thu, 12 Jun 2003 21:26:24 +0400 [thread overview]
Message-ID: <20030612172624.GG7319@namesys.com> (raw)
In-Reply-To: <1055435090.2028.7.camel@terminus.zapto.org>
Hello!
On Thu, Jun 12, 2003 at 05:24:50PM +0100, Herbie Hopkins wrote:
> > Is the hardware starting to fail and doing lots of retries maybe?
> I sure hope not as the drive is only a couple of months old. Booting a
> kernel with CONFIG_REISERFS_CHECK=y dmesg gives me:
> reiserfs:warning: CONFIG_REISERFS_CHECK is set ON
> reiserfs:warning: - it is slow mode for debugging.
> reiserfs: checking transaction log (device 03:07) ...
> journal-1153: found in header: first_unflushed_offset 465,
> last_flushed_trans_id 84176
> journal-1206: Starting replay from offset 465, trans_id 84177
> journal-1299: Setting newest_mount_id to 95
> Using r5 hash to sort names
> ReiserFS version 3.6.25
> which looks normal to me.
What if you turn off this debugging stuff that is certainly slows down all the operations by a lot?
Corresponding kernel option (compile-time) is CONFIG_REISERFS_CHECK
Bye,
Oleg
next prev parent reply other threads:[~2003-06-12 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 14:20 slow mount Herbie Hopkins
2003-06-12 14:18 ` Yury Umanets
2003-06-12 14:35 ` Alex Zarochentsev
2003-06-12 14:39 ` Chris Mason
2003-06-12 14:43 ` Herbie Hopkins
2003-06-12 14:46 ` Oleg Drokin
2003-06-12 15:26 ` Herbie Hopkins
2003-06-12 15:47 ` Herbie Hopkins
2003-06-12 15:56 ` Hans Reiser
2003-06-12 16:24 ` Herbie Hopkins
2003-06-12 17:26 ` Oleg Drokin [this message]
2003-06-12 17:33 ` Herbie Hopkins
2003-06-12 17:38 ` Oleg Drokin
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=20030612172624.GG7319@namesys.com \
--to=green@namesys.com \
--cc=Herbie@Hopkins.net \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.