From: Eric Sandeen <sandeen@sandeen.net>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/4] xfsdump: update to use fallocate
Date: Wed, 21 Aug 2019 14:37:44 -0500 [thread overview]
Message-ID: <98c27715-55db-bdc0-8dcd-8ba4ee3e8080@sandeen.net> (raw)
In-Reply-To: <156633248668.1207741.376678690204909405.stgit@magnolia>
thanks but I actually merged these back in May :D
https://git.kernel.org/pub/scm/fs/xfs/xfsdump-dev.git/commit/?id=36b5cf95733df250fc4401b6a336b7ffc7567b94
On 8/20/19 3:21 PM, Darrick J. Wong wrote:
> Hi all,
>
> This is a series to update the "create file and preallocate blocks"
> code in xfs_restore.
>
> The first patch refactors the existing copy-pasta into a single helper
> function to create and preallocate space in files, as well as removing
> the totally broken ALLOCSP code.
>
> The next two patches fix unchecked return values and insufficient
> unsupported-ioctl code.
>
> The final patch upgrades xfs_restore to try fallocate before RESVSP
> simply because it is the newer API.
>
> This is an extraordinary way to destroy everything. Enjoy!
> Comments and questions are, as always, welcome.
>
> --D
>
next prev parent reply other threads:[~2019-08-21 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 20:21 [PATCH 0/4] xfsdump: update to use fallocate Darrick J. Wong
2019-08-20 20:21 ` [PATCH 1/4] xfs_restore: refactor open-coded file creation code Darrick J. Wong
2019-08-20 20:21 ` [PATCH 2/4] xfs_restore: check return value Darrick J. Wong
2019-08-20 20:21 ` [PATCH 3/4] xfs_restore: fix unsupported ioctl detection Darrick J. Wong
2019-08-20 20:21 ` [PATCH 4/4] xfs_restore: support fallocate when reserving space for a file Darrick J. Wong
2019-08-21 19:37 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-22 16:47 [PATCH 0/4] xfsdump: update to use fallocate Darrick J. Wong
2019-05-06 18:24 ` Darrick J. Wong
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=98c27715-55db-bdc0-8dcd-8ba4ee3e8080@sandeen.net \
--to=sandeen@sandeen.net \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@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.