From: Christian Robert <christian.robert@polymtl.ca>
To: linux-btrfs@vger.kernel.org
Cc: cwillu <cwillu@cwillu.com>
Subject: Re: btrfs: block rsv returned -28
Date: Fri, 24 Feb 2012 21:47:20 -0500 [thread overview]
Message-ID: <4F484BB8.2090601@polymtl.ca> (raw)
In-Reply-To: <CAE5mzvhzsHDU=HU9_MTcp8ptA25tcn7HkxqOE1SNqznvRk9eMQ@mail.gmail.com>
wrong, I tryed to wait until "Load average" got near to zero (couple of minutes)
before unmounting and it changed nothing. None of thoses subvolumes have any data inside
so deleting should be trivial and quick.
Got the kernel backtrace "while" doing the deletes. Not after.
Xtian.
On 2012-02-24 21:37, cwillu wrote:
> On Fri, Feb 24, 2012 at 8:26 PM, Christian Robert
> <christian.robert@polymtl.ca> wrote:
>> Hi,
>>
>> I ran a quite heavy script who create 10,000 subvolumes and then delete
>> thoses 10,000 subvolumes.
>>
>> No problems in the "create" part, but at the "delete" part
>> I got several traceback from the kernel:
>>
> [snip]
>>
>> and finally the partition cannot be unmounted and I had to reboot.
>>
>> well, it's probably not that important, who the hell will be deleting 10,000
>> subvolumes
>> in a 2 minutes timeframe ?
>
> Deletion works in the background, and involves a walk over the
> contents being deleted. I'm fairly sure that unmounting blocks on the
> completion of that background process, which could take quite some
> time in this case.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-02-25 2:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 2:26 btrfs: block rsv returned -28 Christian Robert
2012-02-25 2:37 ` cwillu
2012-02-25 2:47 ` Christian Robert [this message]
2012-02-25 4:55 ` Duncan
2012-02-25 4:31 ` Duncan
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=4F484BB8.2090601@polymtl.ca \
--to=christian.robert@polymtl.ca \
--cc=cwillu@cwillu.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).