The core of the issue here comes down to two things:
First, a power loss to the drive will cause the drive's dirty write cache
to be lost, that data will not make it to disk. Nor do you really want
to turn of write caching on the physical drive. Well, you CAN turn it
off, but
ultipliers and other external enclosure bridges,
high-end SCSI phys and, NVRAM aside (which is arguable), real RAID
hardware. And well-known vendors (fringe SSDs do not count). That
covers 90% of the market and 99% of the cases where protocol reliability
is required.
:> Do you know if that's changed at all with NCQ on modern SATA drives?
:> I've seen people commenting that using tags recovers most, if not all,
:> of the performance lost by disabling the write cache.
:...
I've never tried that combination. Theoretically the 32 tags SATA
supports woul
a very good chipset spec and
vendors took all sorts of liberties.
-Matt
Matthew Dillon
___
freebsd-stable@freebsd.org mailing list
ht
The limitation was ONLY due to a *minor* 32-bit integer overflow in one
or two *intermediate* calculations in the radix tree code, which I
long ago fixed in DragonFly.
Just find the changes in the DFly codebase and determine if they need
to be applied.
The swap space radix
Two additional pieces of information.
The original limitation was more related to DEV_BSIZE calculations for
the buf/bio, which is now 64-bits and thus not applicable, though you
probably need some preemptive casts to ensure the multiplication is
done in 64-bits. There was als
:
:I don't know what's going on, but I've been getting literally hundreds of
:virus/worm-looking emails per hour all day today. I grew tired of it and
:wrote the following Sieve script to filter my mail on the server.
:
:The pseudo-bounce messages were particularly annoying; they're close enough
and
I/O footprint of these nice +20 processes and take steps to significantly
reduce both.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
__
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:Jan Pechanec ([EMAIL PROTECTED]) wrote:
:>
:>On Sat, 6 Mar 2004, Holger Kipp wrote:
:>
:>>I experience a very repeatably but unwanted behaviour w
:
:I would love to, if I could find hardware that reproduces the problem. I
:went shopping for USB thumb drives a while back and only came up with
:working ones.
:
:I have a Soyo KT400 Dragon Lite machine at home.
:
:--
:Doug White| FreeBSD: The Power to Serve
:[EMAIL PROTECT
A DragonFly user noticed that usbd does not seem to get DETACH events
for UMASS devices.
I tracked this down (in the FreeBSD-5 codebase for your convenience)
to line 1382 of usb_subr.c:
/*usbd_add_dev_event(USB_EVENT_DEVICE_DETACH, dev);*/
This line was apparentl
I took a bunch of a photos at USENIX, mainly of BSD related activities.
The photos are now online at:
http://apollo.backplane.com/USENIX2004/
-Matt
Matthew Dillon
Polling should not produce any improvement over interrupts for EM0.
The EM0 card will aggregate 8-14+ packets per interrupt, or more.
which is only around 8000 interrupts/sec. I've got a ton of these
cards installed.
# mount_nfs -a 4 dhcp61:/home /mnt
# dd if=/mnt/x of=/d
do until we hit around 100Khz (10uS delay). Then everything goes to
hell in a handbasket.
Conclusion: 1 hz would probably be a better default then 8000 hz.
-Matt
Matthew Dillon
of processing (e.g. firewall lists) the machine has to do on the packets.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTE
utput.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail
Polling should not produce any improvement over interrupts for EM0.
The EM0 card will aggregate 8-14+ packets per interrupt, or more.
which is only around 8000 interrupts/sec. I've got a ton of these
cards installed.
# mount_nfs -a 4 dhcp61:/home /mnt
# dd if=/mnt/x of=/d
:Matt,
:Any chance of an -stable MFC on these?
:
:-Troy Cobb
: Circle Net, Inc.
: http://www.circle.net
I am going to Cc -stable on the response to this excellent question.
Yes, most of the NFS performance enhancements can be MFC'd relatively
easily. The VN enhancements can be MFC'd
ep
print entryoffsetinblock
And it may be better to take this off the list and into private email.
If I can't figure it out from that I may need access to the dump and
debug kernel binary.
-Matt
:Speaking of mmap, was this DoS every fixed/ commited to stable ?
:
:With
:slag3% limit -h
:cputime unlimited
:filesize32768 kbytes
No. There is no limit on how much memory can be allocated via mmap().
There will soon be a resource limit to help determine which process
ged sheet metal chassis is enough!
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
:
:On Tue, Oct 26, 1999 at 08:03:35PM -0700, Matthew Dillon wrote:
:> Yes, I'll do a cpdup port too.
:
:Thanks, Matt! I know plenty of people that will find this useful.
:
:--
:Jos Backus _/ _/_/_/ "Reliability means never
/usr/ports/misc/cpd
still looking for panic messages.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
: .SH foo, bar, baz
:
:and then a lot of junk text (I appended /etc/rc and /etc/rc.network). Then,
:when I do
:
: nroff -ms foo.ms 2>&1 | less
:
:and quit 'less' straight away, the whole system seems to lockup. ^T
:worked (sometimes), and showed troff using lots of system time (no use
enter into an infinite loop because
the writer believes there is a reader 'reading' when, in fact, the reader
side is stuck in pipeclose(). They two sides then play ping-pong
tsleep/wakeup with each other forever.
-Matt
I intend to MFC the preliminary SMP cleanups I did in current a few
weeks ago back into 4.x. My current plan is to do this on wednesday.
I do not expect there to be any complains since the SMP cleanups appear
to have been working wonderfully in -current for some time now but
:In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
:
:>:I don't see anything justifying an immediate MFC in this patch. Please
:>:allow the normal waiting period to elapse before you MFC.
:>
:>Unless you can justify a reason for it NOT to be MFC'd immediate
There's another good reason to MFC the linux patch on wednesday...
that is, to do it at the same time the SMP cleanup is MFC'd, and that
is because both patch sets require the linux kernel module to be
recompiled and I'd rather not force people to do that twice.
The SMP pat
Judging by your original bug report, Howard, it seems likely that either
the machine or the network the machine is sitting on is being attacked
and the machine is running out of some resource (probably network mbufs).
Increasing the NMBCLUSTERS any more will probably not help.
:Hi,
:
:I'm wondering if anything exists to set this.. When you create an INET
:socket
:without the 'TCP_NODELAY' flag the network layer does 'naggling' on your
:transmitted data. Sometimes with hosts that use Delayed_ACK
:(net.inet.tcp.
:delayed_ack) it creates a dead-lock where the host will
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
: 65074 python 0.06 CALL madvise(0x287c5000,0x70,_MADV_WILLNEED)
: 65074 python 0.027455 RET madvise 0
: 65074 python 0.58 CALL madvise(0x287c5000,0x1c20,_MADV_WILLNEED)
: 65074 python 0.016904 RET madvise 0
: 65074 python 0.000179 CALL madvise(0x287c6000,0x1950,_
to the underlying
media... i.e. issue real I/O. So msync() can't be a NOP if you go by
the OpenGroup specification.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]
ned.
--
My recommendation is to fix physio(). User programs that do not supply
aligned buffers clearly don't care about performance, so the kernel
can just back the pbuf with memory and copyin/out the user data.
rt of dynamic memory
allocations deep in the filesystem that ZFS and HAMMER need to do.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
:Oliver Fromme wrote:
:
:> Yet another way would be to use DragoFly's "Hammer" file
:> system which is part of DragonFly BSD 2.0 which will be
:> released in a few days. It supports remote mirroring,
:> i.e. mirror source and mirror target can run on different
:> machines. Of course it is still
:Went from 10->15, and it took quite a bit longer into the backup before
:the problem cropped back up.
Try 30 or longer. See if you can make the problem go away entirely.
then fall back to 5 and see if the problem resumes at its earlier
pace.
--
It could be temperature rela
l give some clue as to the
actual cause.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org maili
ctures. 32G of swap needs
around 2-4MB of wired ram.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@free
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
:> -vfs.nfs.realign_test: 22141777
:> +vfs.nfs.realign_test: 498351
:>
:> -vfs.nfsrv.realign_test: 5005908
:> +vfs.nfsrv.realign_test: 0
:>
:> +vfs.nfsrv.commit_miss: 0
:> +vfs.nfsrv.commit_blks: 0
:>
:> changing them did nothing - or at least with respect to nfs t
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to &
A couple of things to note here. Well, many things actually.
* Turning off write caching, assuming the drive even looks at the bit,
will destroy write performance for any driver which does not support
command queueing. So, for example, scsi typically has command
queuein
as with 3Ware) boot support. ZERO.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinf
makes background fsck problematic
and risky.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Guys, please don't start a flamewar. And lhmwzy we discussed this
on the DFly lists. It's really up to them... that is, a programmer
who has an interest, inclination, and time. It isn't really fair to
try to push it.
I personally believe that the FreeBSD community as a whole
Also, if you happen to have a handheld GPS unit, it almost certainly
has a menu option to tell you the sunrise and sunset times at your
current position.
-Matt
___
freebsd-stable@freebsd.org ma
One of the problems with resource management in general is
that it has traditionally been per-process, and due to the
multiplicative effect (e.g. max-descriptors * limit-per-descriptor),
per-process resources cannot be set such that any given user is
prevented from DDOSing the s
If you can swing a routed network that will definitely have the fewest
complications.
For a switched network if_bridge and ARP have to be integrated, something
I just finished doing in DragonFly, so that all member interfaces of the
bridge use *only* the bridge's MAC for all tr
: mmap: 43.400u 9.439s 2:35.19 34.0%16+184k 0+0io 106994pf+0w
: read: 41.358u 23.799s 2:12.04 49.3% 16+177k 67677+0io 0pf+0w
:
:Observe, that even though read-ing is quite taxing on the kernel (high
:sys-time), the mmap-ing loses overall -- at least, on an otherwise idle
:system -
se then leaving them B_DELWRI in
the buffer cache because now the VM pages are all soft-busied).
-Matt
Matthew Dillon
___
free
MART page to appease
techies :-)
These particular WDs (2TB Caviar Green's) are slow drives. 5600 rpm,
100MB/sec. But they are also very quiet in operation and seem to
be quite power efficient.
-Matt
The Silicon Image 3124A chipsets (the PCI-e version of the 3124. The
original 3124 was PCI-x). The 3124A's are starting to make their way
into distribution channels. This is probably the best 'cheap' solution
which offers fully concurrent multi-target NCQ operation through a port
:Correction -- more than likely on a consumer motherboard you *will not*
:be able to put a non-VGA card into the PCIe x16 slot. I have numerous
:Asus and Gigabyte motherboards which only accept graphics cards in their
:PCIe x16 slots; this """feature""" is documented in user manuals. I
:don't kno
It is actually a security issue to automatically destroy snapshots based
on whether a filesystem is full, even automatically generated snapshots.
Since one usually implements snapshots to perform a function you wish
to rely on, such as to retain backups of historical data for auditi
Jim's original report seemed to indicate that the filesystem paniced
on mount even after repeated fsck's.
That implies that Jim has a filesystem image that panics on mount.
Maybe Jim can make that image available and a few people can see if
downloading and mounting it reproduc
fsck's memory usage is directly related to the number of inodes and
the number of directories in the filesystem. Directories are
particularly memory intensive.
I've found on my backup system that a UFS1 filesystem with 40 million
inodes is about the limit that can be fsck
gmented you are going to be doing the seeks
anyway, probably.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-sta
I guess nobody mentioned the obvious thing to check: Make sure
TCP keepalive is turned on.
sysctl net.inet.tcp.always_keepalive=1
If you don't do this then dead TCP connections can build up, particularly
on busy servers, due to the other end simply disappearing.
Without
:On May 29, 2008, at 3:12 PM, Matthew Dillon wrote:
:>I guess nobody mentioned the obvious thing to check: Make sure
:>TCP keepalive is turned on.
:>
:>sysctl net.inet.tcp.always_keepalive=1
:
:
:Thanks Matt.
:
:I also thought that a keepalives were not running and s
ausing the data sent from the server to build up
and for the client's buffer space to run out, and start advertising the
0 window.
-Matt
Matthew Dillon
<[EMAIL
:This is exactly what we're seeing, it's VERY strange. I did kill off
:Apache, and all the FIN_WAIT_1's stuck around, so the kernel is in
:fact sending these probe packets, every 60 seconds, which the client
:responds to... (most of the time).
Ach. Now that I think about it, it is sti
It might be a reasonable bandaid, though.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.
:How would decreasing the polling time fix this? I do not understand
:the semantics/behaviour of NTP very well.
:
:Taken from the manpage:
:
: maxpoll maxpoll
: These options specify the minimum and maximum poll intervals for
: NTP messages, in seconds to the power of two. The
or managing VM spaces. Once those features were in place
it didn't take long for me to create a 'vkernel' platform that linked
against libc and used the new system calls.
-Matt
Matthew Dillon
mplete an utter nightmare to maintain.
Any failure at all could lead to a completely unrecoverable system.
-Matt
Matthew Dillon
&l
:I'm trying to probe this as well as I can, but network stacks and sockets have
:never been my strong suit ...
:
:Robert had mentioned in one of his emails about a "Sockets can also exist
:without any referencing process (if the application closes, but there is still
:data draining on an open so
ron job that dumps memory statistics once a minute to a file then
break each report with a clear-screen sequence and cat it in a really
big xterm window.
-Matt
Matthew Dillon
Basically maxswzone is the amount of KVM the kernel is willing to
use to store 'struct swblock' structures.
These are the little structures that are stuck onto VM objects and
specify which pages in the VM object(s) correspond to which pages
of swap, for any swapped out data tha
p UMA memory statistics that would be beneficial as well.
I just find it hard to imagine that any system would actually be using
that much swap, but hey! :-)
-Matt
Matthew D
a once-a-10-minutes cron job to
append pstat -s, vmstat -m, and vmstat -z to a file.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
, check it out. My assumption is that rconfig would compile
nearly without modification on a FreeBSD box.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
and takes
forever to read.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.or
ahahhaha. OMG.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailm
:Marc G. Fournier wrote:
: > For those that remmeber the other day, I had that swzone issue, where I ran
out
: > of swap space? I just about hit it again today, swap was up to 99% used
... I
: > was able to get a ps listing in, and there were a whack of find processes
: > running ...
: >
: >
:IV> > Upd: on GENERIC/amd64 kernel I got the same errors.
:IV>
:IV> Do you perhaps run with TSC timecounter? (that's the only cause I've notice
:IV> that can generate this message).
:
:Nope:
:
:[EMAIL PROTECTED]:~> sysctl kern.timecounter
:kern.timecounter.tick: 1
:kern.timecounter.choice: TSC(-1
n/kern_resource.c (in FreeBSD-6.x).
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.free
00 hz.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
issue with SMP.
I'm afraid there isn't much more I can do to help, other then to make
suggestions on tests that you can run that will hopefully ring a bell
with another developer.
-Matt
Matt
:s,/kernel,/boot/kernel/kernel, ;-)
:
:well, strange enough result for me:
:
:(kgdb) print cpu_ticks
:$1 = (cpu_tick_f *) 0x8036cef0
:
:Does this mean that kernel uses tsc? sysctl reports
:
:kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-100)
:kern.timecounter.hardw
o make sure it properly dereferencing the underlying device and properly
destroys the (now unwritable) dirty buffers.
-Matt
Matthew Dillon
<
The vast majority of machine installations just slave their dns off
of another machine, and because of that I do not think it is particularly
odious to require some level of skill for those who actually want to set
up their own server.
To that end what I do on DragonFly is simp
A friend of mine once told me that the only worthwhile RAID systems are
the ones that email you a detailed message when something goes south.
-Matt
___
freebsd-stable@freebsd.org mailing list
http://l
The basic answer is that HZ is almost, but not quite irrelevant.
If a process blocks another will immediately be scheduled. More
importantly, if an interrupt driven event (keyboard, tty, network,
disk, etc) wakes a process up the scheduler has the ability to force
an IMMEDIATE
n), whereas the
scheduler has to make decisions based on counting quantums.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freeb
My experience with one of our people trying to do the same thing
w/ HAMMER... we got it working, but it is not necessarily cleaner.
I'd rather just boot from a small UFS /boot partition on 'a' (256M
or 512M), followed by swap on 'b', followed by the big-ass root
partition on '
What we wound up doing was splitting tvtohz() into two functions.
tvtohz_high(tv)
Returned value meets or exceeds requested time. A minimum value
of 1 is returned (really only for {0,0}.. else minimum value is 2).
tvtohz_low(tv)
Returned value might be short
:
: [Moved from -current to -stable]
:
:צ×ÔÏÒÏË 21 ÂÅÒÅÚÅÎØ 2006 16:23, Matthew Dillon ÷É ÎÁÐÉÓÁÌÉ:
:> You might be doing just writes to the mmap()'d memory, but the system
:> doesn't know that.
:
:Actually, it does. The program tells it, that I don't
o use a larger block size.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-
te out a sequential file (on any operating system, not
just BSD).
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebs
:The file stops growing, but the network bandwidth remains at 20Mb/s. `Netstat
:-s' on the client, had the following to say (udp and ip only):
If the network bandwidth is still going full bore then the program is
doing something. NFS retries would not account for it. A simple
test f
something to do either with the
way the filesystem being exported was mounted on the server, or the
export line in /etc/exports.
-Matt
Matthew Dillon
My guess is that you are exporting the filesystem as a particular
user id that is not root (i.e. you do not have -maproot=root: in the
exports line on the server).
What is likely happening is that the NFS client is trying to push out
the pages using the root uid rather then the
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FS partition. The NFS client would then use that user id
for all write I/O operations.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
_
it should allow the
I/O operation to run as long as some non-root user would be able to
do the I/O op.
-Matt
Matthew Dillon
<[EM
em is not secure
(and never was). It is fairly trivial for a client to supply file
handles that are outside of the subdirectory tree that was exported.
-Matt
Matthew Dillon
:Actually, I can not agree here -- quite the opposite seems true. When running
:locally (no NFS involved) my compressor with the `-1' flag (fast, least
:effective compression), the program easily compresses faster, than it can
:read.
:
:The Opteron CPU is about 50% idle, *and so is the disk* pr
:Yes, they both do work fine, but time gives very different stats for each. In
:my experiments, the total CPU time is noticably less with mmap, but the
:elapsed time is (much) greater. Here are results from FreeBSD-6.1/amd64 --
:notice the large number of page faults, because the system does no
1 - 100 of 155 matches
Mail list logo
