https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229972
--- Comment #4 from Patrick Mackinlay ---
Yesterday I had some time to investigate this further and believe I have found
the problem (at least for me).
I created a bhyve vm and installed a simple vanilla FreeBSD 11.1 instance with
a single
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206217
Mark Linimon changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230258
Jakub Kruszona-Zawadzki changed:
What|Removed |Added
CC||a...@moosefs.com
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172
--- Comment #3 from Max Burke ---
I have tried enabling the verbose boot option with the out-of-the-box 11.2
kernel but this has provided no extra diagnostic information.
(Unless I'm doing it wrong, which may be the case :)
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211304
Navdeep Parhar changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230260
--- Comment #5 from Conrad Meyer ---
If you're able, please try this patch and report if the performance is
improved:
--- a/sys/fs/fuse/fuse_vfsops.c
+++ b/sys/fs/fuse/fuse_vfsops.c
@@ -341,7 +341,7 @@ fuse_vfsop_mount(struct mount *mp)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230260
--- Comment #4 from Conrad Meyer ---
Doh, I totally missed some other hardcoded 4096 in the FUSE kernel support
code. I see two instances:
1. fuse_internal_init_callback: if the fuse_init_out version is below 7.5, we
explicitly limit max_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228409
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228500
Mark Linimon changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230286
Bug ID: 230286
Summary: panic: lookup: ni_pathlen underflow to -3
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Keywords:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172
--- Comment #2 from Pavel Minaev ---
Same exact problem with
FreeBSD-12.0-CURRENT-amd64-20180709-r336134-mini-memstick.img
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|p...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172
Pavel Minaev changed:
What|Removed |Added
CC||int...@gmail.com
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230242
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230160
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230144
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230273
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230274
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229852
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualizat...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229882
Mark Linimon changed:
What|Removed |Added
Assignee|standa...@freebsd.org |b...@freebsd.org
Component
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229972
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229970
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229977
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|g...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229986
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|f...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229990
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualizat...@freebsd.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229995
Mark Linimon changed:
What|Removed |Added
Keywords||panic, regression
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230003
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230008
Mark Linimon changed:
What|Removed |Added
Keywords||panic
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230017
Mark Linimon changed:
What|Removed |Added
Summary|service ntpd onefetch |service ntpd onefetch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230017
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230032
Mark Linimon changed:
What|Removed |Added
Keywords||i915, regression
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230040
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230048
Mark Linimon changed:
What|Removed |Added
CC||i...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230077
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230073
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|virtualizat...@freebsd.org
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230081
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|thre...@freebsd.org
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230082
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|b...@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230120
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230137
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|toolch...@freebsd.org
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230168
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|p...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230187
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230184
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|toolch...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230220
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|k...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230235
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230246
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|g...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230275
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|r...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230260
--- Comment #3 from Conrad Meyer ---
You might try bumping the size of 'buf' in fuse_buf_fd_to_fd in libfuse and
seeing if that changes the size of IO submitted to your filesystem.
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230260
--- Comment #2 from Conrad Meyer ---
libfuse itself has a crappy splice(2) reimplementation that hardcodes a 4k
buffer size. I'm not sure that's being used here, but it's a possibility.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230260
--- Comment #1 from Conrad Meyer ---
Hm, my reading of fuse_read_biobackend suggests we should be bound by MAXBSIZE,
which is 64k on head. Is it smaller on 11? Nope, it's been 64k since ~2000.
I wonder where the 4k is coming from.
--
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230230
--- Comment #1 from Yuri Victorovich ---
As it turned out, this header is made obsolete beginning c++17, so we probably
shouldn't add it.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230258
--- Comment #3 from Conrad Meyer ---
Here's a changelog of protocol additions we don't have:
https://github.com/libfuse/libfuse/blob/master/include/fuse_kernel.h
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230258
--- Comment #2 from Conrad Meyer ---
Re: lowlevel_notify_inval_entry, note that this was added in protocol 7.12 and
FreeBSD only supports 7.8:
https://libfuse.github.io/doxygen/fuse__lowlevel_8h.html#ab14032b74b0a57a2b3155dd6ba8d6095
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230258
--- Comment #1 from Conrad Meyer ---
FreeBSD's bufcache caches file contents by default. This can be worked around
by having userspace open files with the O_DIRECT option, or by having your FUSE
filesystem's FUSE_OPEN handler return FOPEN_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230275
gustavo.sca...@collabora.com changed:
What|Removed |Added
See Also||https://bugs.freebsd.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230275
Bug ID: 230275
Summary: [GCE] Run growfs on every boot
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230230
Yuri Victorovich changed:
What|Removed |Added
CC|ema...@freebsd.org |d...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230092
Conrad Meyer changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230274
Bug ID: 230274
Summary: linuxulator and cloudabi don't handle multiple mbufs
in a control message chain
Product: Base System
Version: CURRENT
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230092
--- Comment #11 from gustavo.sca...@collabora.com ---
Change is inside, shouldn't this be closed now?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #8 from Alexey ---
Power off ? or simple /sbin/reboot ? you will need power off + power on. not
reboot or shutdown -r if timeouts already started.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #7 from skillcoder ---
Unfortunately, this workaround was not help me.
After add "vfs.zfs.cache_flush_disable=1" to "/boot/loader.conf" and reboot.
I still have the same log after boot:
Aug 2 01:30:32 skillcoder kernel: ahcich
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #6 from Alexey ---
(In reply to Alexey from comment #5)
But problem is, if we check spec for HGST HUS722T1TALA604 drive,
https://www.hgst.com/sites/default/files/resources/Ultrastar-7K2-EN-US-DS.pdf I
do not see the drive is "S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230273
--- Comment #2 from Conrad Meyer ---
Based on the implementation of linux_select in compat/linux/linux_misc, I don't
see how the wrapper would introduce 100ms of latency.
--
You are receiving this mail because:
You are the assignee for th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230273
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223327
Ed Maste changed:
What|Removed |Added
Blocks||228911
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230273
Bug ID: 230273
Summary: linux_select CALL is very slow (100 ms)
Product: Base System
Version: 11.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Sever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #5 from Alexey ---
Yes, looks like vfs.zfs.cache_flush_disable=1 hide the problem. (At list
servers with raidz1 ZFS pool, who used to start timeouts after no more 2 days
uptime, now have 6 days uptime and no any timeout on conso
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230269
Brooks Davis changed:
What|Removed |Added
CC||bro...@freebsd.org
--- Comment #2 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227808
doktornotor changed:
What|Removed |Added
CC||doktorno...@mailinator.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230269
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
Resolution
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230269
Bug ID: 230269
Summary: failed to make llvm 2.7
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230220
--- Comment #14 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kib
Date: Wed Aug 1 19:06:55 UTC 2018
New revision: 337055
URL: https://svnweb.freebsd.org/changeset/base/337055
Log:
Avoid assertion in /dev/ufssusp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230220
--- Comment #13 from Dexuan Cui ---
(In reply to Edward Tomasz Napierala from comment #12)
kib is right. As I described in comment #9, the design of Hyper-V live back up
of a guest is that: the Hyper-V host only backs up the guest disk imag
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212539
--- Comment #2 from Mark Johnston ---
It's elftoolchain. The issue is still reproducible with at least gcc 6.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169814
--- Comment #3 from Ed Maste ---
Linux ptrace support added in r313809, merged to stable/11 in r316363 - are you
able to test again?
https://reviews.freebsd.org/rS313809
https://reviews.freebsd.org/rS316363
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230082
--- Comment #3 from Yuichiro NAITO ---
(In reply to Bill Sorenson from comment #1)
Thanks for the advise.
Reverting r335939 and r336088 works for me, too.
And I found the attached `bhyverun.patch` works for me without reverting.
Due to la
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230082
--- Comment #2 from Yuichiro NAITO ---
Created attachment 195717
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=195717&action=edit
bhyverun.patch
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=130251
Ed Maste changed:
What|Removed |Added
Resolution|--- |Unable to Reproduce
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212539
--- Comment #1 from Ed Maste ---
Which readelf is this (GNU or ELF Tool Chain)?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing lis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230220
--- Comment #12 from Edward Tomasz Napierala ---
Doesn't it also freeze the rest of the guest state (RAM etc) at the same time?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230220
--- Comment #11 from Konstantin Belousov ---
(In reply to Edward Tomasz Napierala from comment #10)
The freeze on ffs layer is clearly needed to ensure consistent metadata on the
storage. Hypervizor cannot know when all meta buffers are fl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230220
--- Comment #10 from Edward Tomasz Napierala ---
You might want to look at the tool the ffs freeze mechanism was created for:
growfs(8).
There is no equivalent of fsfreeze(8), because it would be inherently
dangerous: you'd easily end up w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230187
--- Comment #2 from Dan McGrath ---
Odd, it's doing it again, and not only is ntp still running, but the time
actually jumped backwards briefly:
remote refid st t when poll reach delay offset jitter
===
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230260
Bug ID: 230260
Summary: [FUSE] [PERFORMANCE]: Performance issue (I/O block
size)
Product: Base System
Version: 11.1-RELEASE
Hardware: Any
URL: https://
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230259
Bug ID: 230259
Summary: [FUSE] [BUG]: File close (release) issue
Product: Base System
Version: 11.1-RELEASE
Hardware: Any
URL: https://robo.moosefs.com/support/fuse_hellow
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230258
Bug ID: 230258
Summary: [FUSE] [BUG]: Attributes caching issue
Product: Base System
Version: 11.1-RELEASE
Hardware: Any
URL: https://robo.moosefs.com/support/fuse_hellowor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230248
Kubilay Kocak changed:
What|Removed |Added
Assignee|b...@freebsd.org|r...@freebsd.org
Flag
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230187
--- Comment #1 from Dan McGrath ---
Seen some more dmesg entries and had ntpq -p command time out trying to talk to
the ntpd:
+[702905] sonewconn: pcb 0xf80055cc8ae0: Listen queue overflow: 193 already
in queue awaiting acceptance (10
89 matches
Mail list logo