On 15 Feb 2013, at 21:01, Lowell Gilbert
wrote:
> Fleuriot Damien writes:
>
>> I'm running 8.3-STABLE and apparently, vmstat won't honor both -i
>> (interrupts) and -w (repeat display every wait delay seconds) flags at
>> the same time.
>> The proble
Fleuriot Damien writes:
> I'm running 8.3-STABLE and apparently, vmstat won't honor both -i
> (interrupts) and -w (repeat display every wait delay seconds) flags at
> the same time.
> The problem also arises with -z.
>
> The manual doesn't mention these flags
Hello list,
I'm running 8.3-STABLE and apparently, vmstat won't honor both -i (interrupts)
and -w (repeat display every wait delay seconds) flags at the same time.
The problem also arises with -z.
The manual doesn't mention these flags being incompatible with -w.
Anyone k
in a crash dump, I see in vmcore.txt.7, In a output of vmstat -z
ITEM SIZE LIMIT USED FREE REQUESTS
FAILURES
16 Bucket:152,0, 150,0,
150,0
32 Bucket:280,0, 165,3,
165,0
64
In the last episode (Jun 01), Morgan Wesström said:
> Hi. This is my "vmstat -i" from my newly installed 7.2-RELEASE-amd64:
>
> # vmstat -i
> interrupt total rate
> irq4: sio0 1105 0
> irq17: em1 u
Hi. This is my "vmstat -i" from my newly installed 7.2-RELEASE-amd64:
# vmstat -i
interrupt total rate
irq4: sio0 1105 0
irq17: em1 uhci1+ 10921807182
irq19: uhci3++ 8196905
Christopher Cowart wrote:
> What is the difference between the SIZE and RES fields of top?
These are the same as the "SIZ" and "RSS" columns in ps(1).
The former is the total virtual size of the process, i.e.
the sum of all pages mapped into the process. The latter
is the part that is currently
w). Maybe better understanding the RES verses SIZE
data along with their relation to threads will explain what's going on
here.
One of my concerns is that a large chunk of memory is going to belong to
the kernel in my configuration. I found vmstat -m (selected output lines
follow):
|
understanding the RES verses SIZE
data along with their relation to threads will explain what's going on
here.
One of my concerns is that a large chunk of memory is going to belong to
the kernel in my configuration. I found vmstat -m (selected output lines
follow):
| libalias 56
I'm running 7.0 on i386.
I'd like to see multiple cpu stats in vmstat.
vmstat
procs memory page disk faults cpu
r b w avmfre flt re pi pofr sr ad0 in sy cs us sy id
0 0 0 398000 77144 7298 1 1 0 5686 12 0 117
> On Tue, Jan 02, 2007 at 02:08:44PM +0400, Tofik Suleymanov wrote:
>> Hello list,
>>
>> looks like `vmstat -i` acts weird on my machine after being 12-15 hours
>> uptime.Here is the iutput of `vmstat -i`:
>>
>> > vmstat -i
>> interrupt
On Tue, Jan 02, 2007 at 02:08:44PM +0400, Tofik Suleymanov wrote:
> Hello list,
>
> looks like `vmstat -i` acts weird on my machine after being 12-15 hours
> uptime.Here is the iutput of `vmstat -i`:
>
> > vmstat -i
> interrupt total
Hello list,
looks like `vmstat -i` acts weird on my machine after being 12-15 hours
uptime.Here is the iutput of `vmstat -i`:
> vmstat -i
interrupt total rate
irq1: atkbd06813 0
irq9: acpi0 5397
eaks.
Also, there is a lot of 'fr' --freed pages, but the ammount of 'fre' -
free pages does not change. what does this mean? It's not freeing
because of forced swapping, because pi/po is 0 almost all the time
vmstat says:
procs memory paged
The 'b' column of vmstat shows pending transactions that require disk I/O.
Does that include NFS connections?
Have a machine with very high numbers in that column, yet when I do top and
select 'm' to show disk activity, the numbers in top are fairly small.
Wondering
On two occasions recently, vmstat has showed me that a
number of processes are blocked due to I/O. At the same
time, the number of disk transactions per second reported is
a small fraction of the disk's capability.
I am thinking some kind of VM config will help, but based on what
I have
[Format recovered--see http://www.lemis.com/email/email-format.html]
Wrapped computer output fixed.
On Tuesday, 1 November 2005 at 10:55:22 +0200, N.Ersen SISECI wrote:
>
> Hello,
>
> I have FreeBSD 5.3-RELEASE-p23.
>
> [EMAIL PROTECTED] vmstat 1
> procs
"N.Ersen SISECI" <[EMAIL PROTECTED]> writes:
> I have FreeBSD 5.3-RELEASE-p23.
>
> [EMAIL PROTECTED] vmstat 1
> procs memory pagedisks faults
> cpu
> r b w avmfre flt re pi po fr sr ad0 cd0 in sy cs us
&g
Hello,
I have FreeBSD 5.3-RELEASE-p23.
[EMAIL PROTECTED] vmstat 1
procs memory pagedisks faults
cpu
r b w avmfre flt re pi po fr sr ad0 cd0 in sy cs us
sy id
0 0 0 69024 424412 371 0 0 0 345 0 0 0 32144 22965 3275
4 7 89
0
When the output from 'vmstat -i' has plus signs after a device, does it have the
same/similar meaning as the plus signs in 'systat 1 -vmstat'?
For example:
irq11: cbb0 an0 130561 59
James
___
[EMAIL PRO
Hello,
I have FreeBSD 4.7 on a P3 933mhz, 18 GB U320 HD, Adaptec 29160
controller, and 512 MB DDR ram. When I ran vmstat -w 3 the b under
processes shows a constant 10 forever and now today it's up to 12. Is this
a concern or is it nothing? Our system is a DNS, web, and email server.
T
On Thu, Jun 26, 2003 at 02:26:30PM -0400, Jason Lieurance wrote:
> Hello,
>
> I have FreeBSD 4.7 on a P3 933mhz, 18 GB U320 HD, Adaptec 29160
> controller, and 512 MB DDR ram. When I ran vmstat -w 3 the b under
> processes shows a constant 10 forever. Is this a concern or is it
Hello,
I have FreeBSD 4.7 on a P3 933mhz, 18 GB U320 HD, Adaptec 29160
controller, and 512 MB DDR ram. When I ran vmstat -w 3 the b under
processes shows a constant 10 forever. Is this a concern or is it nothing?
Our system is a DNS, web, and email server. Thanks.
--
Jason
23 matches
Mail list logo
