Hi
I have been experimenting with putting F2FS onto a NVMe block device. I have
been hitting a kernel panic on mount and was wondering if anyone on the list
had any ideas what might be causing this. I formatted the NVMe block device
using the f2fs-tools version 1.2.0 with default format setting
> Hi Stephen,
>
> On Wed, May 04, 2016 at 10:47:10PM +, Stephen Bates wrote:
> > Hi
> >
> > I have been experimenting with putting F2FS onto a NVMe block device. I
> have been hitting a kernel panic on mount and was wondering if anyone on
> the list had any id
> >
> > One thing I did notice is that fallocate() seems slow (5-6 GB/s) compared to
> other file systems for a 3TiB fallocate() [ext4 performs the same operation in
> under a second on my system)]. Is this typical/expected for F2FS? Could it be
> because I have the IO_TRACE and/or _SECURITY set in
>
> We could figure out how to improve them. :)
>
> I've been preparing two patches under testing right now.
> - f2fs: fallocate data blocks in single locked node page
> - f2fs: read node blocks ahead when truncating blocks
>
> Thanks,
Let me know when and where I can pull these and I can do
