[Bug 226152] panic: handle_written_inodeblock: Invalid link count 65535

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226152

Andriy Gapon  changed:

   What|Removed |Added

Summary|server crash|panic:
   ||handle_written_inodeblock:
   ||Invalid link count 65535

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226141] "zpool remove" causes panic: solaris assert: zio->io_type == ZIO_TYPE_WRITE (0x3 == 0x2)

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226141

Andriy Gapon  changed:

   What|Removed |Added

 CC||m...@freebsd.org

--- Comment #1 from Andriy Gapon  ---
Looks like this could be a fallout from r329732 "7614 zfs device
evacuation/removal".

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226166] [PATCH] fts(3): setting FTS_FOLLOW for children does not work as expected when FTS_NOCHDIR is set

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226166

Bug ID: 226166
   Summary: [PATCH] fts(3): setting FTS_FOLLOW for children does
not work as expected when FTS_NOCHDIR is set
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: jan.kokemuel...@gmail.com
  Keywords: patch

Created attachment 190957
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190957&action=edit
patch to fix FTS_FOLLOW when set on entries returned by fts_children()

Reading the fts(3) man page something like the example below should work. This
sets FTS_FOLLOW on a child named 'symlink' which is a symlink to another
folder. fts_read will now recurse into this folder, even though FTS_PHYSICAL is
set. Right now it won't recurse, however, when FTS_NOCHDIR is also set.

The problem is a stale fts_accpath. This leads to fts_stat() calling stat on
the wrong file. The attached patch attempts to fix this by switching the order
of the fts_stat() and the fts_accpath update.



#include 
#include 
#include 
#include 
#include 

int
main()
{
FTS *fts;
FTSENT *ftsent, *children;
char *fts_args[] = { ".", NULL };

fts = fts_open(fts_args, FTS_PHYSICAL | FTS_NOCHDIR, NULL);
if (!fts) {
err(1, "fts");
}

while ((ftsent = fts_read(fts))) {
fprintf(stderr, "got file: %s\n", ftsent->fts_path);

children = fts_children(fts, 0);

for (FTSENT *child = children; child;
 child = child->fts_link) {
if (!strcmp("symlink", child->fts_name)) {
if (fts_set(fts, child, FTS_FOLLOW)) {
err(1, "fts_set");
}
}
}
}

if (fts_close(fts) < 0) {
warn("fts_close");
}
}

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 222632] connect(2) not available in capability mode

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632

--- Comment #19 from Jan Kokemüller  ---
Has anybody had a chance to look at this yet (disabling connectat/bindat in
capabilities mode when called with AT_FDCWD)? Should I open a new bug report?

Right now it's possible to communicate with other peers when in capabilities
mode without any privileged helper processes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226169] freebsd installer hangs in a loop while creating mirror

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226169

Bug ID: 226169
   Summary: freebsd installer hangs in a loop while creating
mirror
   Product: Base System
   Version: 11.1-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: er...@hyperform.be

Dear,

Thanks for maintaining & supporting FreeBSD.
Having a high end HP elitebook working as a stable NAS solution, the laptop's
battery serving as a cheap UPS, I decided to try building a high-end
workstation using a Lenovo P51.

So a gave the latest FreeBSD a try.
Unfortunately the installer gets stuck when trying to build a pool.
Tried v10.4, v11 (stable) & v12 (latest)

The installer works untill the point it gets stuck in some loop while trying to
create a pool of mirrored Samsung SSD 512 GB MZVLW512HMJP drives with NVMe
controllers.

What is logged in the console is very very similar, if not identical to what is
desribed in bug 211713.

Do not hesitate to query me for more detailed information.
I am prepared to cooperate in any test or procedure to get FreeBSD working on
this box !
Obviously no data is on the laptop, except Windows which I can do without.

Thanks,
Erwin

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226169] freebsd installer hangs in a loop while creating mirror

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226169

Erwin Geeraerts  changed:

   What|Removed |Added

  Component|bin |kern

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226170] gstat does not detect new devices (/dev/gpt/* & /dev/label/*)

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226170

Bug ID: 226170
   Summary: gstat does not detect new devices (/dev/gpt/* &
/dev/label/*)
   Product: Base System
   Version: 11.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: ben.rub...@gmail.com

Hi,

I automatically run gstat upon system startup to feed a performance reporting
tool.
Here is the command launched :
# gstat -B -d -o -s -I30s -f"label/|gpt/"

Some seconds/minutes after system startup, I add some iSCSI disks needed for
production :
# iscsictl -Aa

Unfortunately, gstat does not detect these new disks. Reproductible for each
newly added disk.
I need to restart it so that it will correctly show them.

Actually, as you can see, I filter on "label/|gpt/", to only work on /dev/label
and /dev/gpt devices, to have nicely named devices in my reports.

After some tests, I found that gstat automatically correctly detects the new
/dev/da* devices, but does not detect /dev/gpt/* and /dev/label/* devices.

Another test, let's remove all iSCSI disks :
# iscsictl -Ra
As expected, gstat automatically removes them from its output.
Let's add them again :
# iscsictl -Aa
gstat now automatically correctly shows /dev/gpt/* and /dev/label/* in its
output. Strange behavior !

Thank you very much for your support !

Ben

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226172] [asmc] [patch] Add Support for MacBookAir 7,1 and 7,2

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226172

Bug ID: 226172
   Summary: [asmc] [patch] Add Support for MacBookAir 7,1 and 7,2
   Product: Base System
   Version: CURRENT
  Hardware: amd64
OS: Any
Status: New
  Keywords: patch
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: james.wri...@jigsawdezign.com
  Keywords: patch

Created attachment 190959
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190959&action=edit
asmc module patch

Patch to add support to asmc module for MacBookAir 2015 models.

Please could someone review and commit?

Result of patch running on a MacBookAir 2015 13" model;

# kldload asmc
# sysctl -a | grep asmc

dev.asmc.0.light.control: 0
dev.asmc.0.light.right: 0
dev.asmc.0.light.left: 0
dev.asmc.0.temp.palmrest: 23
dev.asmc.0.temp.mainboardproximity: 22
dev.asmc.0.temp.heatpipe: 25
dev.asmc.0.temp.airflowproximity: 24
dev.asmc.0.temp.wirelessproximity: 26
dev.asmc.0.temp.pchdie: 34
dev.asmc.0.temp.memorybank: 29
dev.asmc.0.temp.thunderboltproximity: 24
dev.asmc.0.temp.pecicpu: 37
dev.asmc.0.temp.pecisa: 0
dev.asmc.0.temp.pecigpu: 38
dev.asmc.0.temp.cpucore2: 38
dev.asmc.0.temp.cpucore1: 37
dev.asmc.0.temp.cpuproximity: 31
dev.asmc.0.temp.cputemp2: 39
dev.asmc.0.temp.cputemp1: 38
dev.asmc.0.temp.enclosure3: 22
dev.asmc.0.temp.enclosure2: 22
dev.asmc.0.temp.enclosure1: 22
dev.asmc.0.fan.0.targetspeed: 1200
dev.asmc.0.fan.0.maxspeed: 6500
dev.asmc.0.fan.0.minspeed: 1200
dev.asmc.0.fan.0.speed: 1200
dev.asmc.0.fan.0.id: Exhaust  
dev.asmc.0.%parent: acpi0
dev.asmc.0.%pnpinfo: _HID=APP0001 _UID=0
dev.asmc.0.%location: handle=\_SB_.PCI0.LPCB.SMC_
dev.asmc.0.%driver: asmc
dev.asmc.0.%desc: Apple SMC MacBook Air 13-inch (Early 2015)
dev.asmc.%parent:

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226154] zfs compile error

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226154

Andriy Gapon  changed:

   What|Removed |Added

 Resolution|--- |Unable to Reproduce
 Status|New |Closed

--- Comment #1 from Andriy Gapon  ---
https://ci.freebsd.org/job/FreeBSD-stable-11-amd64-build/

You didn't provide much details about your circumstances.
For local build issues it's better to seek help on the appropriate mailing
lists (e.g. freebsd-stable).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226175] portsnap fails to delete directories that were deleted from the subversion repository

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226175

Bug ID: 226175
   Summary: portsnap fails to delete directories that were deleted
from the subversion repository
   Product: Base System
   Version: 11.0-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: freebsd-bugs@FreeBSD.org
  Reporter: y...@freebsd.org

Please see the symptoms description in bug#225921 (with the port
devel/oniguruma).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 226175] portsnap fails to delete directories that were deleted from the subversion repository

2018-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226175

Yuri Victorovich  changed:

   What|Removed |Added

 CC||scratch65...@att.net

--- Comment #1 from Yuri Victorovich  ---
*** Bug 225921 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"