Re: [LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling
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 -- To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling
On 02/07/2013 02:06 PM, Boaz Harrosh wrote: [ .. ] 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 -- Dr. Hannes Reinecke zSeries Storage h...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling
On Tue, Jan 29, 2013 at 12:14 AM, Hannes Reinecke h...@suse.de 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. Count me in too -- To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling
On Tue, Jan 29, 2013 at 12:14 AM, Hannes Reinecke h...@suse.de wrote: 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. -- To unsubscribe from this list: send the line unsubscribe linux-scsi in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[LSF/MM TOPIC] Thin provisioning SOFT_THRESHOLD error handling
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 h...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
