From: Matthias Schniedermeyer <ms@citd.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Marc Lehmann <schmorp@schmorp.de>, xfs@oss.sgi.com
Subject: Re: drastic changes to allocsize semantics in or around 2.6.38?
Date: Sun, 22 May 2011 09:59:55 +0200 [thread overview]
Message-ID: <20110522075955.GA2341@citd.de> (raw)
In-Reply-To: <20110522020024.GZ32466@dastard>
On 22.05.2011 12:00, Dave Chinner wrote:
>
> I don't really care what you think the problem is based on what
> you've read in this email thread, or for that matter how you think
> we should fix it. What I really want is your test cases that
> reproduce the problem so I can analyse it for myself. Once I
> understand what is going on, then we can talk about what the real
> problem is and how to fix it.
What would interest me is why the following creates files with large
preallocations.
cp -a <somedir> target
rm -rf target
cp -a <somedir> target
After the first copy everything looks normal, `du` is about the
original value.
After the second run a `du` shows a much higher value, until the
preallocation is shrunk away.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-05-22 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 0:55 drastic changes to allocsize semantics in or around 2.6.38? Marc Lehmann
2011-05-20 2:56 ` Dave Chinner
2011-05-20 15:49 ` Marc Lehmann
2011-05-21 0:45 ` Dave Chinner
2011-05-21 1:36 ` Marc Lehmann
2011-05-21 3:15 ` Dave Chinner
2011-05-21 4:16 ` Marc Lehmann
2011-05-22 2:00 ` Dave Chinner
2011-05-22 7:59 ` Matthias Schniedermeyer [this message]
2011-05-23 1:20 ` Dave Chinner
2011-05-23 9:01 ` Christoph Hellwig
2011-05-24 0:20 ` Dave Chinner
2011-05-23 13:35 ` Marc Lehmann
2011-05-24 1:30 ` Dave Chinner
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=20110522075955.GA2341@citd.de \
--to=ms@citd.de \
--cc=david@fromorbit.com \
--cc=schmorp@schmorp.de \
--cc=xfs@oss.sgi.com \
/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.