From: Jeff Mahoney <jeffm@suse.com>
To: Linux FS Maling List <linux-fsdevel@vger.kernel.org>
Subject: [LSF/MM TOPIC][ATTEND] ENOSPC notification for squishy targets
Date: Mon, 18 Feb 2013 14:35:45 -0500 [thread overview]
Message-ID: <51228291.7050809@suse.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hannes touched on this briefly in his thin provisioning topic, where
he'd like some sort of notification system to allow tools to
automatically adjust thin provisioned storage either by extension or
trimming.
I'd like to extend the topic to notification for similar conditions
that can occur with btrfs snapshots, especially in the case where they
happen automatically. Hints from the file system when ENOSPC is
approaching and automatic cleanup would be useful would help user
experience quite a bit.
Likewise, with LVM snapshots, file systems will encounter EIO when the
CoW device runs out of exception space.
A general way to communicate this information to userspace would be
useful in a bunch of different scenarios.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJRIoKRAAoJEB57S2MheeWyLN4P/2obs0VYultPhyW+C9il6EKD
uUpLfGlyALYKxSjBEPSTUNOWA3mlWg1TqBc459mMEitgR4pK0aM97yPsOVktGyib
d0oRpmsd3K6LAwUQw4iTgq+sY+Zvc9329zUl6n0HgnwPYagUI9uZeYfG6/A+k5LR
ebyn0oIG2hEemEy9AYaBHVqNotz4sBlX2UgsIuGGxfuzs7eG0EPVz0C57eRqW00+
7AtC6rmDvNT5U17ozVuOzJGYu/4yZDhxhD4roCxFDM6NkQCa1NA4TVRDJZ9ChhqC
N4wFancoqQmwm1Ra9+RQ21ErpMCfTDfIQx+ntnaFL3x2kLWla5CDhtkSWoMk9Ejk
FPKVcaov1SaianCsEJS5pMCXylw3wCKhuS0TiJJ90BmLIAMP/ETo9vsnftJqbReD
fd1qX/bzSJ+h9cBK/+XNUVUXia91PrAy8xHwPAB9AhaT0FCA11udpWVEy8R6C7gh
vV9kgB7WCAjzI7UHXYAEDbF/whayCyTwjTqFfDbMQ98053AF0qHd+pkazcUPSRcg
w85kAMGcZflBtt7bqmADLmowp+ANGKhqbYHCINSx/eeaId2WUSRAoswAsS7Gr3TB
S7bjSNfJrxfLJHfM9BFqu9PyqHQrYHQxVzo9qa3dD5qEAhcPtsacO5qzcDJOSHcF
Ys3admefajoNllMWcyLq
=8UKB
-----END PGP SIGNATURE-----
reply other threads:[~2013-02-18 19:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51228291.7050809@suse.com \
--to=jeffm@suse.com \
--cc=linux-fsdevel@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).