Date: Tue, 23 Aug 2016 09:27:56 +0200 From: Frederic Chardon <chardon.frederic@gmail.com> To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: kern.proc.pathname failure while booting from zfs Message-ID: <CAMODbkmV8UNXX76Zi2utgvkw_bZyyJqcBa8e382Hp9oyDpbZXw@mail.gmail.com> In-Reply-To: <CAMODbkm%2BZ0TA_MHjcMtzieHgE3Q9akpTuYSVzRgb-bS5vTN=ug@mail.gmail.com> References: <CAMODbkmNkkOuaKydLJvDPGkKUSGvcFauzyRCAvgX-9quoDUoWw@mail.gmail.com> <CAMODbkmjNK0RNHA1A2Tq0TQ%2BPaqh1RGr-AnsV6BbP1M01e434w@mail.gmail.com> <CAMODbkm%2BZ0TA_MHjcMtzieHgE3Q9akpTuYSVzRgb-bS5vTN=ug@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 20 ao=C3=BBt 2016 22:03, "Frederic Chardon" <chardon.frederic@gmail.com>=
a
=C3=A9crit :
>
> Hi
>
> I see a strange interaction between zfs on root and kern.proc.pathname
> on my laptop. Whenever I try to use gcore it fails with:
> gcore 1023
> gcore: kern.proc.pathname failure
>
> However, gcore /usr/local/bin/zsh 1023 is working properly.
>
> I made some tests booting from usb stick (fresh installworld, no
> src.conf, no make.conf, GENERIC kernel)
> What works: having / on ufs and importing a zfs pool later on.
> What doesn't: having / on zfs, whatever the settings for checksum,
> compression, or normalization.
>
> Both 11-stable and 12-current behave this way. Current from may-june
> worked properly.
> adb, chromium and virtualbox as well stopped working at approximately
> the same time, however I don't know if it is linked ("truss -f adb
> start-server" shows that garbage is passed to execl after forking).
>
> Any idea what's going on? Does anybody else see this?
>
> Thanks!
Nobody else have this problem? I reinstalled the system from scratch and
still gcore fails with the same error, even in single user mode.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMODbkmV8UNXX76Zi2utgvkw_bZyyJqcBa8e382Hp9oyDpbZXw>