On Tue, Dec 16, 2014 at 02:11:19AM +0500, Alexander E. Patrakov wrote: > Hello. > > At least in 3.16 and 3.17, btrfs has an SSD-killer bug: > https://bugzilla.kernel.org/show_bug.cgi?id=85581 > > It is now fixed in 3.18, but the fix has not yet propagated to the stable > kernels. To avoid further hardware damage, please consider including this > upstream commit into all stable trees where it applies: > > commit 25ce459c1af138f95a3fd318461193397ebb825b > Author: Liu Bo <bo.li.liu@xxxxxxxxxx> > Date: Wed Sep 10 12:58:50 2014 +0800 > > Btrfs: fix loop writing of async reclaim > > One of my tests shows that when we really don't have space to reclaim > via > flush_space and also run out of space, this async reclaim work loops on > adding > itself into the workqueue and keeps writing something to disk according > to > iostat's results, and these writes mainly comes from commit_transaction > which > writes super_block. This's unacceptable as it can be bad to disks, > especially > memeory storages. > > This adds a check to avoid the above situation. > > Signed-off-by: Liu Bo <bo.li.liu@xxxxxxxxxx> > Signed-off-by: Chris Mason <clm@xxxxxx> > > Thanks, > -- > Alexander E. Patrakov > -- > To unsubscribe from this list: send the line "unsubscribe stable" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html Thank you, I'll queue it for the 3.16 kernel. Cheers, -- Luís -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html