Skip to contentSkip to conversation

Thin provisioning SOFT_THRESHOLD error handling

LSF/MM TOPIC Hannes Reinecke 5 participants 6 messages Jan 29, 2013 – Feb 7, 2013

Subsystems (2)
lore
Share & tools
lore
#0 lore 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

Signature · 8 lines
Dr. Hannes Reinecke		      zSeries & Storage
[email protected]			      +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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#1 lore raw
Quoted 2 lines · Hannes Reinecke

I would like to discuss at LSF the possible implementations and handling mechanism for this kind of failure scenarios.

I'd be interested in that discussion. With my Pure hat on, our array can generate these thin provisioning threshold unit attentions, and it would be nice if Linux did something intelligent with them.

- R.

#2 lore raw
In reply to Hannes Reinecke

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 12 lines · Hannes Reinecke

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).

Quoted 6 lines

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-----

#3 lore raw
In reply to Hannes Reinecke
Quoted 11 lines · Hannes Reinecke

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).

Quoted 6 lines

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.

Count me in too

#4 lore raw
In reply to Hannes Reinecke
Quoted 12 lines · Hannes Reinecke

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).

Quoted 7 lines

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

Quoted 4 lines

Cheers,

Hannes

#5 lore raw

On 02/07/2013 02:06 PM, Boaz Harrosh wrote:
[ .. ]

Quoted 8 lines

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.

You might want to look at Ewan Milnes patch-set ...

Cheers,

Hannes

Signature · 8 lines
Dr. Hannes Reinecke		      zSeries & Storage
[email protected]			      +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-fsdevel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html