From: "George Spelvin" <linux@horizon.com>
To: linux-ext4@vger.kernel.org
Cc: linux@horizon.com
Subject: debugfs feature request: dump sparse files as sparse.
Date: 13 Nov 2012 23:07:57 -0500 [thread overview]
Message-ID: <20121114040757.16656.qmail@science.horizon.com> (raw)
When dumping a file with some messed-up block pointers, I discovered
that I had a huge, and fully allocated destination file. (ls -s on the
dump displayed some very large number, even though the original file
only had about 8 blocks allocated.)
It wouldprobably make more sense to seek over the gaps to create a
sparse file.
next reply other threads:[~2012-11-14 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 4:07 George Spelvin [this message]
2012-11-15 14:46 ` [PATCH] debugfs: dump a sparse file as a new sparse file Zheng Liu
2013-01-01 2:08 ` Theodore Ts'o
2013-01-01 12:33 ` Zheng Liu
2013-01-01 20:10 ` George Spelvin
2013-01-01 20:57 ` Theodore Ts'o
2013-01-01 21:25 ` George Spelvin
2013-01-01 22:47 ` Theodore Ts'o
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=20121114040757.16656.qmail@science.horizon.com \
--to=linux@horizon.com \
--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 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.