https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265463
--- Comment #1 from Evgeniy ---
Created attachment 235502
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=235502&action=edit
Forgot to put db
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
Daniel Menelkir changed:
What|Removed |Added
CC||dmenel...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #67 from Chris ---
In reply to Daniel (comment #66)
Smartmontools are available on FreeBSD. The drives show no issue with the
smartmontools. I believe there is a compatibility issue between the drives and
the motherboard. I upd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258056
Keith White changed:
What|Removed |Added
Attachment #235480|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258056
--- Comment #19 from Alan Somers ---
The whole point of 7b8622fa220b9c08041102f638f848c48e022644 was to make
/dev/fuse pollable. It is pollable now, in other languages. So there's
probably still a bug somewhere in the Go code. Does Go wr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #68 from Daniel Menelkir ---
(In reply to Chris from comment #67)
I know, I mean to try different platforms.
And to mention, this is an specific issue with 13.1+ZFS, I don't think it's
something of the motherboard itself, since
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258056
--- Comment #20 from Keith White ---
Not an issue for you!
I think the issue is how go itself "thinks" kqueue works with a file or device.
The comments in src/os/file_unix.go would seem to indicate that files that are
always ready to writ
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265466
Bug ID: 265466
Summary: Shutdown Causes System Reboot on FreeBSD 13
Product: Base System
Version: 13.1-STABLE
Hardware: amd64
OS: Any
Status: New
Se
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #69 from Chris ---
(In reply to Daniel Menelkir from comment #68)
The issue happens with 12 as well and requires vfs.zfs.cache_flush_disable=1
and a power cycle to clear.
I don't think it's a just a ZFS issue since a reboot ju
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258056
--- Comment #21 from Keith White ---
(In reply to Keith White from comment #20)
For more background reading.
It looks like the go bug report 19093 (referenced in src/os/file_unix.go) gives
more detail as to what go "assumes" and why regula
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258056
Alan Somers changed:
What|Removed |Added
Summary|sys/fs/fuse: commit |lang/go118: musn't poll
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262743
--- Comment #5 from Michał Skalski ---
Thank you very much for the clues
(In reply to Mark Millard from comment #4)
Yes, using default value 12 (I used stock qemu VM image):
# sysctl vm.pageout_oom_seq
vm.pageout_oom_seq: 12
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253445
--- Comment #38 from Jonathan Vasquez ---
I've converted my existing one layer set up to a two layer one so I now have
the option of either using bectl or doing the snapshotting/cloning myself, and
still be compatible with the boot environm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262743
--- Comment #6 from Mark Millard ---
(In reply to Michał Skalski from comment #5)
Use of the likes of vm.pageout_oom_seq=120 should delay any kills for
failures to reclaim enough memory to reach FreeBSD's target figure
for free RAM.
This
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258056
--- Comment #23 from Keith White ---
Added upstream as https://github.com/golang/go/issues/54100
Assuming it gets noticed and incorporated, this FreeBSD bug could be "closed"
or changed to "not an issue..."
Thanks asomers for all your hin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265471
Bug ID: 265471
Summary: loader: /boot/lua/menu.lua boots kernel from original
bootenv when bootenv is changed
Product: Base System
Version: 13.1-RELEASE
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265472
Bug ID: 265472
Summary: /boot/loader: lua autoboot timer restarts if menu
password is set
Product: Base System
Version: 13.1-RELEASE
Hardware: Any
OS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265471
crah...@gmail.com changed:
What|Removed |Added
Attachment #235516|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #70 from Daniel Menelkir ---
(In reply to Chris from comment #69)
A zpool error isn't supposed to clear with a reboot. The test I've mentioned
can be done with a live USB.
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
--- Comment #71 from Chris ---
(In reply to Daniel Menelkir from comment #70)
I didn't get any zpool errors. The system was hanging with cam status timeouts.
Since I changed the disks the performance of the system improved considerably.
20 matches
Mail list logo
