Re: f2fs bug: Unable to mount big volumes in kernel 4.5

[Matthias Prager <linux@matthiasprager.de>]

Am 23.03.2016 um 13:54 schrieb David Gnedt:
> Hello,
> 
> On 2016-03-22 21:36, Jaegeuk Kim wrote:
>> So, could you check the patch that I replied or the same patch that I attached
>> here?
>> That should dynamically fix this issue when mounting f2fs.
> 
> I had to manually apply the patch on 4.5 sources. I have attached the modified
> patch. If you want, I can also test based on the recent f2fs kernel tree.
> 
> I have used a similar setup as in my last test. The new patch fixes the old
> volumes as expected:
> [144530.446411] F2FS-fs (loop0): Fix alignment : done, start(4063232)
> end(1953505792) block(1949433856)
> [144530.447700] F2FS-fs (loop0): Fix alignment : done, start(4063232)
> end(1953505792) block(1949433856)
> 
> Additionally, the fixed volumes mount without problems on all kernel versions I
> tested: 4.5.0 x86_64, 4.5.0+patchv2 x86_64
> I haven't tried 4.4.6 x86_64 yet, but if you want I can do that later today.
> 
> The only thing that might not be as expected is that the alignment is also fixed
> when the volume is mounted read-only.
I will get to my tests later today, but wanted to comment on this
detail. Writing on a read-only fs is a no go! There usually is a reason
why someone mounts an filesystem read-only and f2fs should not simply
ignore such a flag.

> 
> Best regards,
> David Gnedt
> 


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140