From d2cecb4ecc0f6f59c41817c2d0d89ab46dfc6d74 Mon Sep 17 00:00:00 2001 From: Sebastian Messmer Date: Fri, 22 Jul 2016 20:44:06 +0200 Subject: [PATCH] Disable large_read fuse option, since it's not used in new fuse versions anyhow and makes problems when fuse is run in user mode linux. --- src/fspp/fuse/Fuse.cpp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/fspp/fuse/Fuse.cpp b/src/fspp/fuse/Fuse.cpp index d62d1c72..20168f8a 100644 --- a/src/fspp/fuse/Fuse.cpp +++ b/src/fspp/fuse/Fuse.cpp @@ -250,8 +250,9 @@ vector Fuse::_build_argv(const bf::path &mountdir, const vector _add_fuse_option_if_not_exists(&argv, "subtype", _fstype); _add_fuse_option_if_not_exists(&argv, "fsname", _fsname.get_value_or(_fstype)); // TODO Also set read/write size for osxfuse. The options there are called differently. - argv.push_back(_create_c_string("-o")); - argv.push_back(_create_c_string("large_read")); // large_read possibly not necessary because reads are large anyhow, but it doesn't hurt. + // large_read not necessary because reads are large anyhow. This option is only important for 2.4. + //argv.push_back(_create_c_string("-o")); + //argv.push_back(_create_c_string("large_read")); argv.push_back(_create_c_string("-o")); argv.push_back(_create_c_string("big_writes")); return argv;