linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13909] md5sum on 3GB file is constantly hanging
Date: Mon, 10 Aug 2009 13:58:46 GMT	[thread overview]
Message-ID: <200908101358.n7ADwklF026243@demeter.kernel.org> (raw)
In-Reply-To: <bug-13909-13602@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=13909





--- Comment #12 from Michael B. Trausch <mike@trausch.us>  2009-08-10 13:58:44 ---
You said that the md5sum is hanging in the R state, yes?  If so, it's not
hanging at all.  It's still computing the MD5 sum.  What sort of disks are you
using (IDE/SCSI/SATA)?  What sort of CPU (cat /proc/cpuinfo)?  How much RAM
(free)?

mbt@zest:~$ time md5sum sample.3gb 
c698c87fb53058d493492b61f4c74189  sample.3gb

real    0m12.017s
user    0m8.561s
sys    0m3.276s

This is on a system that isn't heavily loaded, with a 3.0Gbps SATA II drive
holding the file.

Try this to see if it really is hanging or not.  Install the "pv" utility.  It
is available from http://www.ivarch.com/programs/pv.shtml -- and in many
distributions (I can say for certain that it is in Ubuntu's repositories at the
very least, and am pretty sure that it's on Debian and RH repositories, too).

Then, run:

cat YOUR_3GB_FILE | pv | md5sum

This will show you how much data is being pushed through the pipe, and at what
rate of speed.  My system is able to push about 200MB/s through pv.  This will
give you a better, visual indication of what is going on.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2009-08-10 13:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 10:44 [Bug 13909] New: md5sum on 3GB file is constantly hanging bugzilla-daemon
2009-08-04 17:10 ` [Bug 13909] " bugzilla-daemon
2009-08-05  4:27 ` bugzilla-daemon
2009-08-08 10:03 ` bugzilla-daemon
2009-08-08 17:10 ` bugzilla-daemon
2009-08-08 19:41 ` bugzilla-daemon
2009-08-08 19:41 ` bugzilla-daemon
2009-08-08 19:42 ` bugzilla-daemon
2009-08-08 19:54 ` bugzilla-daemon
2009-08-08 20:38 ` bugzilla-daemon
2009-08-10  9:31 ` bugzilla-daemon
2009-08-10 13:33 ` bugzilla-daemon
2009-08-10 13:58 ` bugzilla-daemon [this message]
2009-08-10 14:11 ` bugzilla-daemon
2009-08-10 14:13 ` bugzilla-daemon
2009-08-10 14:34 ` bugzilla-daemon
2009-08-10 15:11 ` bugzilla-daemon
2009-08-10 15:58 ` bugzilla-daemon
2009-08-10 17:41 ` bugzilla-daemon
2009-08-10 18:21 ` bugzilla-daemon
2009-08-10 18:39 ` bugzilla-daemon
2009-08-10 20:11 ` bugzilla-daemon
2009-08-10 20:13 ` bugzilla-daemon
2009-08-10 21:13 ` bugzilla-daemon
2009-08-10 21:24 ` bugzilla-daemon
2009-08-10 21:59 ` bugzilla-daemon
2009-08-11 18:47 ` bugzilla-daemon
2009-08-11 22:35 ` bugzilla-daemon
2009-08-15 13:54 ` bugzilla-daemon
2009-08-17 14:31   ` Ric Wheeler
2009-08-17 10:23 ` bugzilla-daemon
2009-08-17 14:29 ` bugzilla-daemon
     [not found] <bug-13909-13602@https.bugzilla.kernel.org/>
2012-06-13 14:35 ` bugzilla-daemon
2012-06-13 14:35 ` bugzilla-daemon

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=200908101358.n7ADwklF026243@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 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).