From: Hannes Reinecke <hare@suse.de>
To: lsf-pc@lists.linux-foundation.org
Cc: Linux-scsi@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling
Date: Tue, 29 Jan 2013 09:14:22 +0100 [thread overview]
Message-ID: <510784DE.3000509@suse.de> (raw)
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.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-01-29 8:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 8:14 Hannes Reinecke [this message]
2013-02-05 0:06 ` [LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling Roland Dreier
2013-02-05 2:22 ` Jeff Mahoney
2013-02-05 17:07 ` Kent Overstreet
2013-02-07 13:06 ` Boaz Harrosh
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=510784DE.3000509@suse.de \
--to=hare@suse.de \
--cc=Linux-scsi@vger.kernel.org \
--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).