From: "krzf83@gmail.com " <krzf83@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: unlink directory with files (rm -d)
Date: Sat, 13 Aug 2011 23:59:34 +0200 [thread overview]
Message-ID: <CAJ1PRSnJHJ+fEgYRv3xN+3hzcvtreNZrnqJUszmoK8YjVCn4VA@mail.gmail.com> (raw)
In-Reply-To: <CAJ1PRS=9obyg-FRq=V6pZ7J=tccYA_UXWvNzF-6SaywL6rBY9g@mail.gmail.com>
I wonder if it would be possible to implement instant unlinking
directory with files in it. Since btrfs is based on b trees it could
be possible. Filesystem would have to "loose" all information on
directory and object in it, and allow overwriting this information.
This would be great feature, because everyone knows that recursive
deleting large directories, with milions of files require huge io
traffic.
next parent reply other threads:[~2011-08-13 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ1PRS=9obyg-FRq=V6pZ7J=tccYA_UXWvNzF-6SaywL6rBY9g@mail.gmail.com>
2011-08-13 21:59 ` krzf83@gmail.com [this message]
2011-08-14 8:03 ` unlink directory with files (rm -d) Sergei Trofimovich
2011-08-14 14:18 ` krzf83@gmail.com
2011-08-14 14:20 ` krzf83@gmail.com
2011-08-15 15:58 ` Chris Mason
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=CAJ1PRSnJHJ+fEgYRv3xN+3hzcvtreNZrnqJUszmoK8YjVCn4VA@mail.gmail.com \
--to=krzf83@gmail.com \
--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).