public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Horrible TrueCrypt performance
Date: Tue, 10 Jan 2012 01:20:24 +0100	[thread overview]
Message-ID: <4F0B8448.4040605@wonkology.org> (raw)

Hi there!

I have to copy some 100 G of files from one to another USB drive. Both
are formatted with NTFS, the destination drive already has a truecrypt
container file where I need to store the data into.

This is sort of working, but the speed is waayyyy too slow. After about
four hours, only 8 G were copied.

Looking at the cp -r output shows I see a bunch of files being
processed, then the output stops for some minutes. Sometimes for half an
hour.

Top shows the mount.ntfs-3g process writing to the destination using all
resources of one of my two cores. iotop -d 10 shows this process mainly.
What I find strange is that this process is also reading from the drive
I am copying to, 1600 K/s compared to 260 K/s writing speed. Huh?? And
sometimes there is no I/O from this process during the ten seconds of
sampling time. I sampled for about half an hour, and iotop -oa shows
that only 20 MB were written. This will never finish.

I used this command to mount the truecrypt container:
truecrypt --fs-options=uid=1000,umask=0007 -k /home/wonko/my.key
/media/My USB Drive/my_container /mnt
Adding 'async' to the fs-options did not help.

Any ideas? I've never used TrueCrypt before.

	Wonko



             reply	other threads:[~2012-01-10  0:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10  0:20 Alex Schuster [this message]
2012-03-06 14:41 ` [gentoo-user] Horrible TrueCrypt performance Alex Schuster
2012-03-06 21:44   ` Frank Steinmetzger

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=4F0B8448.4040605@wonkology.org \
    --to=wonko@wonkology.org \
    --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