From: Mike Kazantsev <mk.fraggod@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Anybody tried shake defragmenter?
Date: Fri, 7 Aug 2009 09:56:56 +0600 [thread overview]
Message-ID: <20090807095656.765dfbb6@malediction> (raw)
In-Reply-To: <49bf44f10908041126h3e991956ta3a3fd397778ff4f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
On Tue, 4 Aug 2009 11:26:26 -0700
Grant <emailgrant@gmail.com> wrote:
> >> Yeah, that's when I'm hearing the HD access I didn't hear before.
> >> I run miro and it's downloading several torrents all the time.
> >> It never made a sound before, but now there's a rhythmic grinding
> >> sound when miro is running, maybe because the HD is more full now.
> >> Could shake help with this? To find out, should I be running it
> >> on the partially downloaded torrents?
> >
> > Well, bittorent does not download in sequential order, so it is
> > constantly doing random reads and writes. You may not be able to
> > avoid the HD grinding during this kind of activity. Download to a
> > RAM drive or SSD or something perhaps.
Note that this problem can also be (easily?) solved on software level by
pre-allocating files (like "dd if=/dev/zero of=file").
Sure, that won't make writes sequential, but that should guarantee that
resulting file would be as non-fragmented as fs allows at a time of
it's creation.
In fact, rtorrent (and libtorrent) seem to have such a feature, prehaps
other clients should have it somewhere, as well.
http://libtorrent.rakshasa.no/ticket/460
> Is there any tool available to show which files are being written to
> any any given time? iotop is great for watching the I/O rate and
> which process is responsible, but sometimes I wonder which files are
> being written. For example, miro is showing a constant 3.5Mbps write
> in iotop, and I only have 50kbps downloading and 30kbps uploading.
> I'd really like to know what is being written to.
Check out sys-fs/inotify-tools (need inotify enabled in kernel).
--
Mike Kazantsev // fraggod.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-08-07 3:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 20:22 [gentoo-user] Anybody tried shake defragmenter? Grant
2009-08-03 20:29 ` Albert Hopkins
2009-08-03 20:46 ` [gentoo-user] " Grant Edwards
2009-08-03 20:51 ` [gentoo-user] " Thierry de Coulon
2009-08-03 21:07 ` Alan McKinnon
2009-08-06 18:59 ` Dirk Heinrichs
2009-08-03 21:05 ` Paul Hartman
2009-08-03 21:11 ` Alan McKinnon
2009-08-03 21:16 ` [gentoo-user] " Grant Edwards
2009-08-03 21:50 ` Alan McKinnon
2009-08-04 9:21 ` Volker Armin Hemmann
2009-08-06 18:57 ` Dirk Heinrichs
2009-08-03 21:33 ` [gentoo-user] " Dale
2009-08-03 21:50 ` Paul Hartman
2009-08-03 23:48 ` Grant
2009-08-04 1:01 ` Paul Hartman
2009-08-04 18:26 ` Grant
2009-08-07 3:56 ` Mike Kazantsev [this message]
2009-08-07 4:36 ` Stroller
2009-08-05 0:58 ` Dan Farrell
2009-08-05 14:42 ` Grant
2009-08-06 18:11 ` Dan Farrell
2009-08-07 23:22 ` Grant
2009-08-08 13:51 ` Alex Schuster
2009-08-09 15:47 ` Grant
2009-08-07 2:29 ` meino.cramer
2009-08-07 15:33 ` Grant
2009-08-07 16:07 ` meino.cramer
2009-08-08 5:40 ` meino.cramer
2009-08-10 15:01 ` Paul Hartman
2009-08-10 15:18 ` Dale
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=20090807095656.765dfbb6@malediction \
--to=mk.fraggod@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox