From: "Jonáš Vidra" <vidra.jonas@seznam.cz>
To: reiserfs-devel@vger.kernel.org
Cc: Georgios Tsalikis <georgios@tsalikis.net>
Subject: Re: Two Reiser4 FSs in the same HDD cause head seek panic?
Date: Thu, 26 May 2016 07:04:53 +0200 [thread overview]
Message-ID: <op.yh10ef1jhogzsi@i17b> (raw)
In-Reply-To: <ni15m1$hf6$1@ger.gmane.org>
On Tue, 24 May 2016 10:58:53 +0200 Georgios Tsalikis
<georgios@tsalikis.net> wrote:
> I happened to format a rootfs partition and another one for /home with
> Reiser4. It proved to be a disaster. Apart from the slow boot times
> (expected from this drive) even after reaching a functional GUI the disk
> kept doing I/O like crazy. When /home became Btrfs the issue ceased. My
> other computer that uses an entire drive formatted with Reiser4 is nice
> and silent as well.
How large are the disks? The long boot time may be (at least partially)
caused by bitmap loading – try mount option “dont_load_bitmap”.
This won't help you with seeking *after* boot, though. It will actually
make it worse.
Do you have a proper IO scheduler set? What does
“cat /sys/block/sdX/queue/scheduler” say? (Replace sdX with the correct
identifier.)
Is there anything interesting in the system logs? I'm assuming there isn't.
--
Jonáš Vidra, vidra.jonas@seznam.cz
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-05-26 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 8:58 Two Reiser4 FSs in the same HDD cause head seek panic? Georgios Tsalikis
2016-05-25 10:22 ` doiggl
2016-05-26 0:15 ` Georgios Tsalikis
2016-05-26 6:00 ` doiggl
2016-05-27 8:05 ` 'Installing your Linux Distribution on Reiser4.' - [Found this as a guide] doiggl
2016-05-26 5:04 ` Jonáš Vidra [this message]
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=op.yh10ef1jhogzsi@i17b \
--to=vidra.jonas@seznam.cz \
--cc=georgios@tsalikis.net \
--cc=reiserfs-devel@vger.kernel.org \
/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.