From: Jeff Mahoney <jeffm@suse.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: Mon, 04 Feb 2013 21:22:45 -0500 [thread overview]
Message-ID: <51106CF5.4020807@suse.com> (raw)
In-Reply-To: <510784DE.3000509@suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/29/13 3: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.
I'd be really interested in discussion on this as well. I can see a
bunch of different uses for this.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJREGz0AAoJEB57S2MheeWy7j8QAKzFRhdtXXMjU/x/S2HZ9TO6
BZCCPN9b5TmUKFWfnSxJ62AqcE0rHkUkTvKIHXdGXUgGP//YR2xkX82xDTtQCUCD
iCj+Dq7MlEFblFLUOC/EjYN5dv4DmGlYxmDrkvVjZcBURbMzijtKik0GqEZ/SI5E
XtilHxyoppdQDvR64g+Tlbwfmp9pyZjBY9in2JZVw7g5oWzrUw+IWZO9S06MUFUc
ZZwdzauYi1y6rDlS9fT9PtbLpCOc0UuUFTvkc1zeKMhSZJSxcIuixMNvR1LnGpZB
XxbpNLKr9O6+bb5/KycjKgbGLDWXXxYX2/5RZ3nNZCxP3FSgnY9lL+9zcgP2FY4D
XcOeif0AJQQEmd2NSl9KjBWzk3LFgelNEz2rsYedSN6CZjOLTK2jpllQM5+h5X0q
FPs3R1sh2OQ62P84JEFD821Teo3Aj3GlkMmIaUsMqaYQi/UZ4p4NVb9U7eExBA0Z
EhV34hjLqs7PVHPajk84gWc291cgXaQj7NH9Ga/7oqBVVF3ouRGDbYKEX2riJMk7
p72sEzi/xT/uGU+lXUDoFr4JUZWTEaKjjbZbN2/UTk+G+MZiwi0Xy6i2YFby9UuH
SuQET55bJHOjzwPbb5uW7WSbJQLmIxp072aA3cK27E7MT2G4RKuVnpj8MlboraDT
uZQPxtndwpC58nWtHHdu
=HI+u
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-05 2:22 UTC|newest]
Thread overview: 7+ 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 [this message]
2013-02-05 17:07 ` Kent Overstreet
2013-02-07 13:06 ` Boaz Harrosh
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=51106CF5.4020807@suse.com \
--to=jeffm@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.