https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266879
--- Comment #25 from David ---
ok so is there a way to disable all write cache in fuse?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266879
--- Comment #24 from David ---
ok so is there a way to disable all write cache in fuse?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266879
--- Comment #23 from Alan Somers ---
(In reply to David from comment #21)
I really can't help you. I'm an expert on fuse, not gluster. You need help
from Daniel, or perhaps from upstream. If you can provide a trace of fuse
operations, th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266879
--- Comment #22 from David ---
another issue probably related to this:
after a few days a sever would drop gluster mounts due to memory exhaustion
pid 911 (glusterfsd), jid 0, uid 0, was killed: failed to reclaim memory
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267871
Bug ID: 267871
Summary: /usr/bin/rs compile fails after udate to c++
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Sever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267654
--- Comment #10 from Li-Wen Hsu ---
I tried to newfs a partition which is directly on da0 (OS disk), it works and
doesn't have any checksum error. I think this means that there should be
something different in os disk (da0) and data disks
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267846
--- Comment #3 from O. Hartmann ---
Setting also
var_run_autosave="YES"
in rc.conf[.local]
followed by
service var_run restart
seems to fullfill the expected purposes. Still, it is confusing. As mentioned
earlier, setting ONLY
var_ru
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267846
--- Comment #2 from O. Hartmann ---
(In reply to Graham Perrin from comment #1)
Hello,
I didn't assume that it is set to YES, the explanation for
var_run_autosave
states that it is active only for "restoring" purposes - assuming at boot
