From: "Ken D'Ambrosio" <ken@jots.org>
To: linux-btrfs@vger.kernel.org
Subject: du reporting odd file sizes during copy.
Date: Wed, 6 Oct 2010 08:52:02 -0400 (EDT) [thread overview]
Message-ID: <23ef6090f815f34d606450a5a34f57a0.squirrel@webmail.jots.org> (raw)
Hi, all. I was copying two 6-GB DVD images yesterday, and while
monitoring the copy progress, noticed that du would show a trend that
*generally* headed toward the final files' sizes, but on occasion would
hop backward, thusly:
root@hal-9000:/shared/ISOs# while true; do du * ; sleep 10; echo;done
1151808 SolidWorks_2008_32-bit.iso
1928784 SolidWorks_2008_64-bit.iso
1072032 SolidWorks_2008_32-bit.iso
1763280 SolidWorks_2008_64-bit.iso
1044384 SolidWorks_2008_32-bit.iso
2097152 SolidWorks_2008_64-bit.iso
1481248 SolidWorks_2008_32-bit.iso
2183184 SolidWorks_2008_64-bit.iso
The images did copy, but I'm just curious as to what the mechanics were
behind du's seemingly non-linear reporting. (If it makes any difference,
one copy was coming in via an ssh pipe from a different machine; the other
was being copied from the local CD drive. Both were using "cat" to write
the files.)
Thanks,
-Ken
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
reply other threads:[~2010-10-06 12:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=23ef6090f815f34d606450a5a34f57a0.squirrel@webmail.jots.org \
--to=ken@jots.org \
--cc=linux-btrfs@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).