Hi, Am 29.09.2016 um 12:03 schrieb Adam Borowski: > On Thu, Sep 29, 2016 at 09:27:01AM +0200, Stefan Priebe - Profihost AG wrote: >> Am 29.09.2016 um 09:13 schrieb Wang Xiaoguang: >>>>> I found that compress sometime report ENOSPC error even in 4.8-rc8, >>>>> currently >>>> I cannot confirm that as i do not have anough space to test this without >>>> compression ;-( But yes i've compression enabled. >>> I might not get you, my poor english :) >>> You mean that you only get ENOSPC error when compression is enabled? >>> >>> And when compression is not enabled, you do not get ENOSPC error? >> >> I can't tell you. I cannot test with compression not enabled. I do not >> have anough free space on this disk. > > Disabling compression doesn't immediately require any space -- it affects > only newly written data. What you already have remains in the old > compression setting, unless you defrag everything (a side effect of > defragging is switching existing extents to the new compression mode).
Yes i know that but most workload is creating reflinks to old files and modify data in them. So to create a good test i need to defrag and uncompress all those files. Greets, Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
