From: Clemens Eisserer <linuxhippy@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: slow deletion of files
Date: Mon, 12 Jul 2010 22:30:20 +0200 [thread overview]
Message-ID: <AANLkTim2GsB-1BKaDUDbvzWkvNRi3YKe7c2iiGm6nRS9@mail.gmail.com> (raw)
In-Reply-To: <4C3A27A0.6090907@gmail.com>
Hi,
>> during my testing of btrfs I found out,
>> that deletion of directory with many files (many millions) takes veeeery
>> long (it is running two weeks now and did not finish).
Same for me. I moved back to ext4 on my backup-drive because deleting
old backups created with BackInTime took forever to delete.
Another reason I moved away was btrfs corrupted, and btrfsck is still
not able to repair it.
I really like btrfs but in my opinion it has still a long road to go
and declaring it stable in 2.6.35 is quite optimistic at best.
- Clemens
next prev parent reply other threads:[~2010-07-12 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 14:59 slow deletion of files Lubos Kolouch
2010-07-11 20:20 ` Konstantinos Skarlatos
2010-07-12 20:30 ` Clemens Eisserer [this message]
2010-07-12 20:32 ` Clemens Eisserer
2010-07-12 21:33 ` Tracy Reed
2010-07-13 9:29 ` Sander
2010-07-13 1:12 ` 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=AANLkTim2GsB-1BKaDUDbvzWkvNRi3YKe7c2iiGm6nRS9@mail.gmail.com \
--to=linuxhippy@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).