On 9/28/21 9:15 AM, Rodney W. Grimes wrote:
On Tue, Sep 28, 2021 at 9:48 AM Rodney W. Grimes
wrote:
^^^
re-guid the pool on first boot.
Isnt the proper place to solve this lack of Unique UUID creation
in the tool(s) that are creating the zfs pool in the first place.
F
On 2021-Oct-21, at 16:24, Mark Millard wrote:
> On 2021-Oct-21, at 11:53, Mark Millard wrote:
>
>> On 2021-Oct-21, at 08:27, Tomoaki AOKI wrote:
>>
>>> On Thu, 21 Oct 2021 07:40:36 -0700
>>> Mark Millard via freebsd-current wrote:
>>>
On 2021-Oct-21, at 06:14, Gary Jennejoh
On 10/20/2021 1:58 pm, Larry Rosenman wrote:
I have a -CURRENT box that I upgraded yesterday & today, and it no
longer can read NFS mounts from my TrueNAS 12.0-U6 server.
It mounts, but any access garners:
nfsv4 client/server protocol prob err=10020
nfsv4 client/server protocol prob err=10020
t
On 2021-Oct-21, at 11:53, Mark Millard wrote:
> On 2021-Oct-21, at 08:27, Tomoaki AOKI wrote:
>
>> On Thu, 21 Oct 2021 07:40:36 -0700
>> Mark Millard via freebsd-current wrote:
>>
>>>
>>>
>>> On 2021-Oct-21, at 06:14, Gary Jennejohn wrote:
>>>
On Thu, 21 Oct 2021 01:34:47 -0700
Well this is different .. I did a full rebuild (after "rm -rf
/usr/obj/*") this morning and now see ..
===> linux_common (install)
install -T release -o root -g wheel -m 555 linux_common.ko /boot/kernel/
install -T dbg -o root -g wheel -m 555 linux_common.ko.debug
/usr/lib/debug/boot/kernel
On 2021-Oct-21, at 08:27, Tomoaki AOKI wrote:
> On Thu, 21 Oct 2021 07:40:36 -0700
> Mark Millard via freebsd-current wrote:
>
>>
>>
>> On 2021-Oct-21, at 06:14, Gary Jennejohn wrote:
>>
>>> On Thu, 21 Oct 2021 01:34:47 -0700
>>> Mark Millard via freebsd-current wrote:
>>>
I get t
On Thu, 21 Oct 2021 07:40:36 -0700
Mark Millard via freebsd-current wrote:
>
>
> On 2021-Oct-21, at 06:14, Gary Jennejohn wrote:
>
> > On Thu, 21 Oct 2021 01:34:47 -0700
> > Mark Millard via freebsd-current wrote:
> >
> >> I get the following crash (amd64 example shown), as reported
> >> vi
On 2021-Oct-21, at 06:14, Gary Jennejohn wrote:
> On Thu, 21 Oct 2021 01:34:47 -0700
> Mark Millard via freebsd-current wrote:
>
>> I get the following crash (amd64 example shown), as reported
>> via gdb afterwards. (devel/llvm13 is just an example context.)
>>
>> gdb `which dialog4ports` d
On Thu, 21 Oct 2021 01:34:47 -0700
Mark Millard via freebsd-current wrote:
> I get the following crash (amd64 example shown), as reported
> via gdb afterwards. (devel/llvm13 is just an example context.)
>
> gdb `which dialog4ports` devel/llvm13/dialog4ports.core
> . . .
> Core was generated by `
I get the following crash (amd64 example shown), as reported
via gdb afterwards. (devel/llvm13 is just an example context.)
gdb `which dialog4ports` devel/llvm13/dialog4ports.core
. . .
Core was generated by `/usr/local/bin/dialog4ports'.
Program terminated with signal SIGSEGV, Segmentation fault.
10 matches
Mail list logo