linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: "Joseph D. Wagner" <joe@josephdwagner.info>
Cc: linux-ext4@vger.kernel.org
Subject: Re: dump ext4 performance degrades linearly as disk fills
Date: Tue, 17 Jun 2014 10:51:29 -0400	[thread overview]
Message-ID: <20140617145129.GB5054@thunk.org> (raw)
In-Reply-To: <53A04BEB.7000401@josephdwagner.info>

Hmm, I've looked at your dumpe2fs, and the free space looks pretty
good.  Was this taken before or after you ran the backup?

How big are your full and incremental backups?  And were you testing
the time when writing an incremental backup or a full backup?

Finally, can you use the debugfs program, and then use the debugfs's
"extents" commands?   i.e.

% debugfs /dev/heap/u1
debugfs: extents linux-image-3.15.0-00037-g7428869-dbg_3.15.0-00037-g7428869-86_amd64.deb
Level Entries       Logical            Physical Length Flags
 0/ 0   1/  3     0 -     9 16898520 - 16898529     10 
 0/ 0   2/  3    10 -  2047 17518592 - 17520629   2038 
 0/ 0   3/  3  2048 -  9881 17500160 - 17507993   7834 
debugfs:  q

... and send me the output?

Thanks!!

					- Ted

  reply	other threads:[~2014-06-17 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16  5:43 dump ext4 performance degrades linearly as disk fills Joseph D. Wagner
2014-06-16 12:42 ` Theodore Ts'o
2014-06-17 14:08   ` Joseph D. Wagner
2014-06-17 14:51     ` Theodore Ts'o [this message]
2014-06-16 21:48 ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2014-06-19 18:42 Joseph D. Wagner
2014-06-21  0:38 ` Theodore Ts'o
2014-07-29 20:55 ` Phillip Susi
2014-07-29 22:48   ` Joseph D. Wagner
2014-06-20 23:59 Joseph D. Wagner

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=20140617145129.GB5054@thunk.org \
    --to=tytso@mit.edu \
    --cc=joe@josephdwagner.info \
    --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).