From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [RFC] btrfs-progs: Add recursive defrag using -r option
Date: Tue, 17 Sep 2013 06:06:16 +0000 (UTC) [thread overview]
Message-ID: <pan$3fd6b$e557a488$ab986a01$72842fce@cox.net> (raw)
In-Reply-To: 073ec67162396b2ebda9c4ef51c6851993132b68.1379383433.git.fholton@gmail.com
Frank Holton posted on Mon, 16 Sep 2013 22:21:24 -0400 as excerpted:
> I'm working on a patch to add the recursive option to the btrfs
> filesystem defrag command. I'd like some feedback on how the patch looks
> as written. I've added two helper functions, which might need to be
> renamed, one to call the ioctl and one to actually handle the recursion
> into the directory.
>
> Let me know what you think.
Not being a dev I won't comment on that angle, but this will sure help
decomplicate general defragging from a sysadmin angle. Thanks. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-09-17 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 2:21 [RFC] btrfs-progs: Add recursive defrag using -r option Frank Holton
2013-09-17 6:06 ` Duncan [this message]
2013-09-17 13:03 ` David Sterba
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='pan$3fd6b$e557a488$ab986a01$72842fce@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).