> On Mar 22, 2017, at 3:28 AM, Arne wrote:
>
> This is the output of "prtconf -vp":
>
> System Configuration: Supermicro i86pc
> Memory size: 65358 Megabytes
> System
What is the impact of this bug with libnvpair?
a) Is this only responsible for non-working "prtconf"? (I guess
"prtconf" is some kind of system overview tool!?)
b) Is it also responsible for the non-working NVMe SSD?
Original Message
Subject: Re: [OmniOS-discuss] OmniOS
> On Mar 22, 2017, at 12:15 PM, Arne
> wrote:
>
> What is the impact of this bug with libnvpair?
>
> a) Is this only responsible for non-working "prtconf"? (I guess "prtconf" is
> some kind of system overview tool!?)
Correct.
> b) Is it also responsible
> On Mar 22, 2017, at 12:54 AM, Richard Skelton wrote:
>
> Hi Richard,
> The nfsv3rwsnoop.d script shows to offset to the write as 0 is this then not
> a new file?
not necessarily
> TIME(us) CLIENT OP OFFSETBYTES PATHNAME
> 20811423544560
There is no file "/var/adm/messages" and there is no file "messages"
anywhere else either ("find /var -name 'mess*'" returns nothing).
Under "/var/adm" there are only 4 directory ("exacct", "log", "pool",
"streams", all of them are empty) and 2 files: "utmpx" and "wtmpx".
Neither of them
Hi Richard,
The nfsv3rwsnoop.d script shows to offset to the write as 0 is this then
not a new file?
TIME(us) CLIENT OP OFFSETBYTES PATHNAME
20811423544560 xxx.xx.xxx.21 W 0 116
20811423525741 xxx.xx.xxx.50 W 0 5232
20811423528311