https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167562
p...@freebsd.org changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Hi,
You have a bug in the Needs MFC state which has not been touched in 7 or more
days. This email serves as a reminder that you may want to MFC this bug or
marked it as completed.
In the event you have a longer MFC timeout you may update this bug with a
comment and I won't remind you again
Hi,
You have a bug in the Needs MFC state which has not been touched in 7 or more
days. This email serves as a reminder that you may want to MFC this bug or
marked it as completed.
In the event you have a longer MFC timeout you may update this bug with a
comment and I won't remind you again
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=158398
Brooks Davis bro...@freebsd.org changed:
What|Removed |Added
Status|Needs MFC |Issue Resolved
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=158398
--- Comment #9 from Brooks Davis bro...@freebsd.org ---
Reverted in 268415 due to breakage caused by botched testing and poor
documentation in this bug. ae@ reports he did not intend to MFC this change.
--
You are receiving this mail
Hi,
You have a bug in the Needs MFC state which has not been touched in 7 or more
days. This email serves as a reminder that you may want to MFC this bug or
marked it as completed.
In the event you have a longer MFC timeout you may update this bug with a
comment and I won't remind you again
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=131415
--- Comment #3 from ne...@otherware.org ---
Created attachment 147936
-- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147936action=edit
geli prompting
I have two keyboards installed here. None of them will recognize my typing.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=94632
Zach Ploskey z...@ploskey.com changed:
What|Removed |Added
CC||z...@ploskey.com
Hi,
You have a bug in the Needs MFC state which has not been touched in 7 or more
days. This email serves as a reminder that you may want to MFC this bug or
marked it as completed.
In the event you have a longer MFC timeout you may update this bug with a
comment and I won't remind you again
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183401
Allan Jude allanj...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197309
--- Comment #3 from f...@fabiankeil.de ---
The steps work as expected for me. Tested on:
FreeBSD kendra 10.1-STABLE FreeBSD 10.1-STABLE #0 r279989+96d5981(stable/10):
Tue Mar 17 19:45:41 CET 2015 fk@kendra:/usr/obj/usr/src/sys/GENERIC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195683
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194681
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197309
f...@fabiankeil.de changed:
What|Removed |Added
CC||f...@fabiankeil.de
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197309
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Component|kern|bin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197309
--- Comment #5 from f...@fabiankeil.de ---
Note that I'm only using ggated on amd64 systems.
Maybe it's an architecture-specific bug, for example a variable size mismatch.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197309
--- Comment #4 from o...@j.email.ne.jp ---
Really?
I wondered if my local changes caused this although I don't have any ggate
related changes and tried raw image from the FreeBSD official site.
I did the same commands and failed again.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161807
fulle...@over-yonder.net changed:
What|Removed |Added
CC||fulle...@over-yonder.net
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199476
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197309
--- Comment #7 from o...@j.email.ne.jp ---
Yes, the patch fixed the issue and I confirmed that I can establish a
connection.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200048
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
--- Comment #4 from Xenomorph xenomo...@gmail.com ---
This seems to still be an issue as of 10.1-RELEASE-p9 in May of 2015. Has this
really been open since 2011?
I have partition 1 named test1 on da1. /dev/da1p1 is not mounted or in use in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
Andrey V. Elsukov a...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199476
Andrey V. Elsukov a...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200740
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201185
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200740
Andriy Gapon a...@freebsd.org changed:
What|Removed |Added
CC||a...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197309
Kubilay Kocak ko...@freebsd.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201873
Mark Linimon lini...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197309
--- Comment #9 from commit-h...@freebsd.org ---
A commit references this bug:
Author: brueffer
Date: Tue Jul 14 10:49:37 UTC 2015
New revision: 285531
URL: https://svnweb.freebsd.org/changeset/base/285531
Log:
Unbreak ggatec and ggatel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199705
--- Comment #2 from luke...@gmail.com ---
(In reply to Ed Maste from comment #1)
Yes. I do believe this is a rare case in practice. :)
I run into this because I test tools/regression/geom_eli with memguard.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199705
--- Comment #1 from Ed Maste ema...@freebsd.org ---
Testing now.
I believe this will in practice be rare - let me know if you agree:
crypto_dispatch()
returns EINVAL if its argument or the callback function was NULL, and 0
otherwise.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201504
Andrey V. Elsukov a...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-geom@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204233
NGie Cooper changed:
What|Removed |Added
CC||be...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204233
amvandem...@gmail.com changed:
What|Removed |Added
CC||amvandem...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201185
--- Comment #2 from commit-h...@freebsd.org ---
A commit references this bug:
Author: pjd
Date: Fri Jul 10 19:27:20 UTC 2015
New revision: 285363
URL: https://svnweb.freebsd.org/changeset/base/285363
Log:
Spoil even can happen for some
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201185
Pawel Jakub Dawidek p...@freebsd.org changed:
What|Removed |Added
Resolution|--- |FIXED
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199705
Ed Maste ema...@freebsd.org changed:
What|Removed |Added
Assignee|freebsd-geom@FreeBSD.org|p...@freebsd.org
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202868
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198405
Edward Tomasz Napierala changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204969
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204901
Kurt Jaeger changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204901
Kurt Jaeger changed:
What|Removed |Added
Assignee|freebsd-geom@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205343
eu...@grosbein.net changed:
What|Removed |Added
CC||freebsd-geom@FreeBSD.org
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205343
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205026
Edward Tomasz Napierala changed:
What|Removed |Added
Status|Open|In
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205026
Edward Tomasz Napierala changed:
What|Removed |Added
Status|New |Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=132845
Fabian Keil changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=132845
--- Comment #2 from o...@j.email.ne.jp ---
This has been quite a while and I happened to open this after seeing an update.
Looking at the report myself and ggated, ggated grabs all files in the export
file at start time. My report
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207247
Mark Linimon changed:
What|Removed |Added
Summary|GEOM multip |GEOM multipath
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206599
Fabian Keil changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206599
--- Comment #2 from Bachmarc ---
Yes and this I would regard as default because standing in an open door while
changing the lock is what people do... nobody would close the door to install a
new lock to get
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196834
Fabian Keil changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196834
--- Comment #1 from Fabian Keil ---
Created attachment 168685
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=168685=edit
geli setkey: Fix key change from passphrase-based to passphrase-less
I rediscovered
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208305
Fabian Keil changed:
What|Removed |Added
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=134113
Fabian Keil changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209113
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
Dexuan Cui changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #35 from commit-h...@freebsd.org ---
A commit references this bug:
Author: ae
Date: Mon Jul 25 09:12:08 UTC 2016
New revision: 303288
URL: https://svnweb.freebsd.org/changeset/base/303288
Log:
Do not invoke resize method if
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #34 from Andrey V. Elsukov ---
(In reply to Peter Wemm from comment #31)
> Note the "GEOM new disk, 0 bytes" happens before the probe messages.
> Presumably the nature of the original panic we were seeing was
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
Peter Wemm changed:
What|Removed |Added
CC||pe...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #31 from Peter Wemm ---
The first few boot attempts looked like this:
...
(da0:mpt0:0:0:0): UNMAPPED
(da1:mpt0:0:1:0): da0 at mpt0 bus 0 scbus0 target 0 lun 0
da0: Fixed Direct Access SCSI-3 device
da0:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #32 from Peter Wemm ---
It fairly consistently prints one or two 'GEOM new disk .. 0 bytes' before the
disk probe messages but has not crashed. It is usually different disks each
time. And it has not ever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #27 from Andrey V. Elsukov ---
(In reply to Peter Wemm from comment #26)
> On closer examination, the GPT headers on these drives have strange things
> going on. It does look like there's a 6 sector
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
Andrey V. Elsukov changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209113
--- Comment #4 from rday ---
I think you're right, a hard limit would be better. I can't find a maximum
parameter count or a maximum parameter size in the documentation though. I
don't think I'm familiar enough with the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209113
rday changed:
What|Removed |Added
CC||r...@ryanday.net
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #22 from Andrey V. Elsukov ---
I think we need a bit more time to test this, so I don't think it will be in
11.0-release.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #15 from Dexuan Cui ---
Hi all,
I know why g_disk_resize() can't work here when I open da1 for reading after a
disk capacity change:
When /dev/da1 is opened for reading (or writing) every time,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #19 from Dexuan Cui ---
(In reply to Andrey V. Elsukov from comment #18)
Your patch is good and it works per my tests.
Thank you very much, Andrey!
Can you please commit it to the CURRENT branch and can
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #5 from Dexuan Cui ---
(In reply to Andrey V. Elsukov from comment #3)
Thank you Andrey for the detailed instructions!
g_resize_provider() returns at Line 671 and at this line, both 'size' and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #10 from Andrey V. Elsukov ---
(In reply to Edward Tomasz Napierala from comment #9)
> Hm. Okay. The read dd works, because the da(4) driver gets notified about
> the capacity change on the first read
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #9 from Edward Tomasz Napierala ---
Hm. Okay. The read dd works, because the da(4) driver gets notified about the
capacity change on the first read command sent to the disk; basically the disk
responds with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #11 from Edward Tomasz Napierala ---
Hm, you're right.
Dexuan - the g_resize_provider() you're seeing, is that after "camcontrol
reprobe", or after the first read? Can you bump GEOM debugflags and show what
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #7 from Edward Tomasz Napierala ---
Also - correct me if I'm wrong, but even if you don't do reprobe, you still see
the new size of da1 - 50G, so GEOM already "sees" the updated size, it's just
that g_part(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #14 from Dexuan Cui ---
(In reply to Dexuan Cui from comment #13)
When I got the kernel messages in comment 13, dtrace showed this:
[root@decui-b11 ~]# dtrace -n 'fbt::*disk_resize:entry
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #13 from Dexuan Cui ---
(In reply to Edward Tomasz Napierala from comment #11)
With kern.geom.debugflags=253 (log everything except G_T_BIO) and
debug.bootverbose=1, after the disk capacity was changed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #12 from Dexuan Cui ---
(In reply to Edward Tomasz Napierala from comment #11)
Thank you both for the analysis!
The g_resize_provider() is after the first read, and before the "camcontrol
reprobe". I'm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #36 from commit-h...@freebsd.org ---
A commit references this bug:
Author: ae
Date: Mon Aug 1 20:54:54 UTC 2016
New revision: 303637
URL: https://svnweb.freebsd.org/changeset/base/303637
Log:
Do not invoke resize event if
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210661
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
--- Comment #7 from Ben RUBSON ---
I found a workaround for glabel.
At the end of sbin/geom/class/label/geom_label.c, in label_dump, right after
label_metadata_dump();
I added the following :
int fd = g_open(name,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205343
--- Comment #2 from Eugene Grosbein ---
I've upgraded this system to 11.0-STABLE/amd64 r313803 and eventually same
panic occured again:
Unread portion of the kernel message buffer:
panic: poffset=59478637056
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
--- Comment #10 from Ben RUBSON ---
Created attachment 174723
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=174723=edit
patch to add refresh method to glabel
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
--- Comment #37 from commit-h...@freebsd.org ---
A commit references this bug:
Author: ae
Date: Fri Sep 30 03:45:41 UTC 2016
New revision: 306476
URL: https://svnweb.freebsd.org/changeset/base/306476
Log:
MFC r303019:
Use
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211028
Andrey V. Elsukov changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
Kurt Jaeger changed:
What|Removed |Added
Keywords||patch
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
Kurt Jaeger changed:
What|Removed |Added
CC||p...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
--- Comment #14 from Ben RUBSON ---
So, 2 patches attached.
The gpart label can be refreshed automatically (when they are added or
modified), thanks to a patch by Andrey (many thanks Andrey !).
There is however a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
--- Comment #13 from Ben RUBSON ---
Created attachment 174918
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=174918=edit
patch to handle gpart add/modify automatically (thx to Andrey)
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
--- Comment #8 from Ben RUBSON ---
https://github.com/freebsd/freebsd/pull/84
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165745
Garrett Wollman changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=162690
--- Comment #15 from Ben RUBSON ---
Any news regarding these 2 patches ?
Could we think about merging them ?
Thank you very much !
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214721
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205026
--- Comment #2 from commit-h...@freebsd.org ---
A commit references this bug:
Author: trasz
Date: Fri Nov 4 13:51:10 UTC 2016
New revision: 308290
URL: https://svnweb.freebsd.org/changeset/base/308290
Log:
MFC r292210:
Fix kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205026
Edward Tomasz Napierala changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214721
nv...@gmx.com changed:
What|Removed |Added
Severity|Affects Only Me |Affects Many People
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214721
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: cem
Date: Thu Jan 12 06:58:32 UTC 2017
New revision: 311964
URL: https://svnweb.freebsd.org/changeset/base/311964
Log:
g_raid: Prevent tasters from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214721
Conrad Meyer changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218337
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org
1 - 100 of 876 matches
Mail list logo