From: Boaz Harrosh <bharrosh@panasas.com>
To: Hannes Reinecke <hare@suse.de>
Cc: <lsf-pc@lists.linux-foundation.org>, <Linux-scsi@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling
Date: Thu, 7 Feb 2013 15:06:35 +0200 [thread overview]
Message-ID: <5113A6DB.5030703@panasas.com> (raw)
In-Reply-To: <510784DE.3000509@suse.de>
On 01/29/2013 10:14 AM, Hannes Reinecke wrote:
> Hi all,
>
> Thin-provisioned devices have the ability to set a 'soft threshold',
> which is triggered if the real free space for this device is beyond
> this mark.
>
> The intention behind this is to allow the system to induce some
> garbage collection with possibly freeing up unused space.
>
> Initially it would be possible to execute garbage collection on
> filesystems (eg for btrfs).
>
> However, as this concept applies to other areas within the kernel
> (like dm-thinp or even btrfs itself) it might be an idea to have
> a general mechanism / error handling etc in place.
>
> I would like to discuss at LSF the possible implementations
> and handling mechanism for this kind of failure scenarios.
>
Hannes hi!
This is received as an "unit attentions", right?
Will it not be worth while to solve the general "unit attentions"
under udev events, once and for all. Than such a btrfs GC above
can just be a simple oneline udev rule.
(I think that the event-storm problem you had at the time can
be solved with some Kernel side "unit attentions" queue, and
greatly reduce the chance for missed events)
Thanks
Boaz
> Cheers,
>
> Hannes
>
next prev parent reply other threads:[~2013-02-07 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 8:14 [LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling Hannes Reinecke
2013-02-05 0:06 ` Roland Dreier
2013-02-05 2:22 ` Jeff Mahoney
2013-02-05 17:07 ` Kent Overstreet
2013-02-07 13:06 ` Boaz Harrosh [this message]
2013-02-07 13:12 ` Hannes Reinecke
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=5113A6DB.5030703@panasas.com \
--to=bharrosh@panasas.com \
--cc=Linux-scsi@vger.kernel.org \
--cc=hare@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).