Thanks everyone for you input.
Matt Ruzicka - Senior Systems Administrator
Front Range Internet, Inc.
[EMAIL PROTECTED] - (970) 212-0728
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubsc
uffer, which is all FLEX generated (or prewritten) code.
The
> > thing compiler just fine under Linux. Any ideas?
> > Cheers,
> > Randy Hyde
> >
>
> Without seeing the code or the actual error message, I'm
> guessing the answer is 42. Perhaps,
uwk" state) while the vnlru kernel thread does it's thing (which is to
recycle vnodes.)
Either the vnlru kernel thread has to work faster, or the caller has to
sleep less, in order to avoid this lock-step behaviour.
Regards,
--
Matt Emmerton
_
already been discussed and I somehow missed it in my troubleshooting and
research.
Thanks.
Matt Ruzicka - Senior Systems Administrator
FRII
970-212-0728 [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailm
:Matt Dillon wrote:
:>
:> I was doing some installworlds and got a bunch of 'gzcat: Broken pipe'
:> errors at the very end when it was doing 'makewhatis' on various manual
:> directories.
:
:It also only happens if you are running ssh to logon to th
xploits can also
potentially modify that state.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
war:-))
turning it on in /etc/defaults/rc.conf.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ompletely
out then to have a semi-broken DLS test.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
moved, it's likely to be powered down anyway cron is not going to
nor is it supposed to 'catch up' after downtime. Additionally, cron
cannot detect a timezone change without being restarted, so the point
is moot anyhow.
nt to have console access to it.
I can't be the only one having this problem can I?
Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Heeey, thank you guys. That is very useful information. I just got off
the phone with Belkin and my replacement KVM is on the way
Thanks,
Matt
> -Original Message-
> From: Chris Shenton [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, January 24, 2001 10:11 AM
> To: Jos
lmost certainly trivial to implement.
-Matt
:Hi,
:
:I've modified the kerenl to add F_CLOSEM functionality to fcntl.
:(I've seen this in some AIX docs).
:
:The purpose is allow a process to close all its filedescriptors starting
:from a given value
:
:At 10:33 26/01/01 -0800, Matt Dillon wrote:
:> I think it is worth doing. A quick google search shows that
:> the linux folks discussed the AIX thingy in March 1999, but
:> I don't think they actually implemented. From the discussion,
:> it appears that t
it should be in libc and use the fcntl.
I would support one or the other, but not both. I'd recommend the
AIX fcntl API, since it's been around a whole lot longer.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
fine) could do the fcntl(), and if it fails fall
back to close()ing descriptors in a loop. Perfect!
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ortability.
We don't need to pollute it with fancy algorithms that we may decide
we have to 'adjust' every year or two. One of the reasons why binary
compatibility works so well over many years is the simplicity of API.
-Mat
If you need syscalls for experimental ops, just assign high syscall
numbers not likely to be used by others during your experiment. It's
no biggy.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
crash.
-Matt
:On i86 boxes with 4M page capabilities, we want contiguous chunks
:of physical address space for mmaped devices to use those larger pages
:when possible.
:
:In practice, this doesn't happen in applications linked with shared
:libraries when mmap() is u
load. I had missed
a function. The rename undoubtedly saved him hours of kernel crash
debugging.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
-area
basis.
This is why 'swapinfo' (aka pstat -s) takes so long to run.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
the above two routines. swapinfo can
then retrieve the information directly via sysctl. i.e. retrieve
the entire array with a single sysctl.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
think it's a fine idea and it will reduce the system load created
by top, systat -vm, and swapinfo, and allow you to move away from the KVM
interface.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers&qu
do for MFS? A 'mount_md'
would give us instant integration into existing kernel mechanisms,
including startup (/etc/rc) mechanisms.
-Matt
:[cvs-(all|commiters) -> -hackers]
:
:> >> If anybody writes a patch to mdconfig
moment so I can't test it immediately, but
I looked at your code and it looks great! I think this will make using
MD disks in -current as easy s using MFS disks was.
-Matt
:I think that's it. Comments?
when the VM context goes away.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
onsidering the number of disks you need to
manage, something like a NetApp or other completely self contained
RAID-5-capable system for handling the disks is mandatory.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
screw around with sysctl vfs.write_behind! I
should probably just rip that sysctl out. The default heuristic handles
all the cases already).
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
in the kernel config.
In 4.2, the generic kernel has it configured).
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
(also: do not use async mounts with softupdates. Just enable softupdates
with tunefs, then mount the filesystem normally).
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the b
with the number of mbuf clusters,
but I suspect increasing maxusers will do the trick. These
changes require recompiling the kernel.
Also, to make sure... you haven't tweaked any other sysctl's, have
you?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
filesystem no matter how it is mounted (even sync mounted filesystems),
is by calling fsync().
So I would stick with softupdates.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:
:On Mon, 5 Feb 2001, Matt Dillon wrote:
:
:> :file: table is full
:
:> :looutput: mbuf allocation failed
:> :nfs server 172.16.0.101:/bravenet1/home: is alive again
:
:> This sheds a considerable amount of light on the problems...
:> methinks you may have a low '
and loose the
file that was fsync()'d if a crash were to occur just after the fsync().
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Y* a filesystem with softupdates
turned on or a journaling filesystem such as XFS or ReiserFS can be
considered crash-surviveable. Synchronous meta-data updates will not
save you (EXT2FS or FFS without softupdates).
-Matt
To Unsubscribe:
irectories. Any directory under heavy use ... well,
softupdates or a log structured filesystem coupled with judicious
fsync() use is your only real choice.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe free
ee. Only
Journaled filesystems (XFS, ReiserFS) can make similar guarentees.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
o access that file, all the way up to root if necessary.
It doesn't touch other unrelated pending data.
-Matt
:The only filesystems I can see being completely resilient
:against these destructive roll-backs would be LFS and tux2.
:
:reg
ue to. If QMail calls fsync() in a
reasonable manner, then softupdates is perfectly safe and the QMail
FAQ needs to be updated to recommend softupdates rather then
disrecommend it.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
er exceeds the speed of sound on its
outer edge. It isn't actually pushing any air so there will be no sonic
boom or any other major issue to deal with.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe free
:On Tue, 6 Feb 2001, Matt Dillon wrote:
:
:> I did a quick search of the qmail site but couldn't find an email
:> address to report the FAQ issue to. If QMail calls fsync() in a
:> reasonable manner, then softupdates is perfectly safe and the QMail
:> FAQ needs
(I will mention here that, of course, sendmail and postfix are no better
in this regard. This is not a detriment to QMail itself verses other
mailers. Since QMail fsync()'s reasonably, it will be just as reliable
as other existing MTAs).
icult problem to solve and it doesn't do it now. All
softupdates does is guarentee filesystem consistency in the case of a
crash and certain guarentees for what will be crash-recoverable when you
do an fsync().
-Matt
To Unsubscribe:
ly, it will be just as reliable
:> as other existing MTAs).
:
:Does sendmail even use fsync()?
:
:--
:Andre
Yes.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ld legally give away
a floppy with WIN-98 MSDOS installed and the fboot.exe program I would but I
think doing so violates a software license or two.
Matt
> -Original Message-
> From: Paul Saab [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 06, 2001 3:23 PM
> To: Mike Smit
?), it's hard to diagnose.
-Matt
:I went over to postfix to see if it did better.in fact it did on
:freebsd but still same problem with I/O. SOlution from talking to some
:people late last night would be to add another harddrive and stripe it
:with another drive us
ueue per drive) is recommended rather then
striping them all into a single filesystem.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
x27;s
relatively easy to test whether the metadata is being distributed
between the two drives reasonably, just look at the drive lights while
you are newfs'ing.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
ay for reliable crash recovery.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
es (as if a hardlink had been
issued). There is no need for a link() operation followed by a remove().
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
us connections a threaded
program is allowed to handle), and then core dump if one actually does
occur.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
should be sufficient to
guarentee (baring a bug in kernel) that a crash will not result in any
lost mail queue files when using a normal FFS mount (without softupdates).
However, I still recommend using softupdates.
-Matt
To
oftupdates) is one of the last ones.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:
:Matt Dillon wrote:
:
:> Yes. In general softupdates will make the entire filesystem safer.
:
:Does it make sense to use softupdates on file systems like / and
:/usr which have little file creation/removal?
:
:Greg
I have had softupdates turned on for all of my mount points for o
The MAP_NOSYNC section of the manual page has a very good description
of how to use mmap() for IPC, but the MAP_SHARED section could use
some more meat.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
s and so don't look there.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
if all you are doing is editing an occassional
file.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
t any reason to *not*
use softupdates.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ke a huge difference due to temporary
file creation & deletion.
When Kirk first tested softupdates against buildworld, he explicitly
tested it with and without -pipe and found that much of the performance
benefit (for buildworld) occured when not using -pipe.
issue
for your disk subsystem for a second or so (for the larger libraries).
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
n interleave of
1152. First disklabel each disk, then use ccdconfig to stripe the
partition you've configured on each disk all together. You might want
to use postfix rather then qmail, but it's up to you.
-Matt
To Unsubscribe: send mail
way.
But as long as the buffer sizes are reasonable and the library uses
fgets() with the proper length limitation, using a statically allocated
buffer is not a big deal. Most configuration files couldn't have long
lines and still be legal anyway.
for example. It's a bad hack.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ring
themselves), or mmap().
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
e at the cost of a slight
loss in type checking. But I only use it for return values... arguments
are still required to be the proper exact type.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
files (assuming you have
sufficient swap).
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
y Type
/dev/ad0s1b524160 188976 33518436%Interleaved
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
urrently
do.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
FreeBSD device layer makes.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
o gracefully back out of a memory failure. It's a huge
waste of time. I just wrap the routines... safe_strdup(), safe_malloc(),
safe_asprintf()... and the wrappers scream bloody murder and exit if
they get a failure. It's that simple... and far more reliable.
he memory failure can't
occur in the first place).
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:Matt Dillon wrote:
:>
:..
:> the system runs out of memory, even *with* overcommit protection.
:> In fact, all sorts of side effects occur even when the system
:...
:
:That's an assumption.
Ha. Right. Go through any piece of significant code and just see how
mu
even come close.
You think these garbage collection algorithms work by running the
system out of VM and then backing off? That's pure nonsense.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
(owner-freebsd-hackers removed from list)
:You're implying that you are making two calls to create the same
:directory. Am I correct?
:
:The answer is 'maybe'? Depends on the remote NFS server. Matt or one
:of the other NFS gurus may know more, but I wouldn't count
fixed.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ust plain dumb.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
e try to propound that running a machine
out of memory on purpose wouldn't have any unwanted side effects.
That's a new one.. and a good laugh. But it isn't reality.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
people's accounts :-)
isprintf() is in there to prevent extranious escape sequences from
blowing up the other guy's window.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:> is it possible to actually find out whether data hit the disk or not for
:> a particular run of 1-7?
:
:Answer to your question:
:
:Do an msync with MS_SYNC someplace. Also, use MAP_NOSYNC in
:mmap until 4.3 when Matt Dillon plans to make that the default behavior.
I plan on mak
ufficient protection.
-Matt
:Why is the mlock(2) call restricted to the super user instead
:of enforcing it through per-user or per-login class limits?
:I was checking to see if most of the pieces were in place for
:"mlockall(MCL_FUTURE)" and noticed the "
::Along the same lines (matt probably knows the answer) is it
::easy to force paging in and locking down of any memory associated
::with a process so that mlockall(MCL_FUTURE) together with
::an appropriate memorylocked limit gives the requested
::memory semantics? I'd have to check throug
with the new chip fab lithography
standards it's going to be 10 GHz.
We need to find something more interesting then buildworlds to do on
these machines.
-Matt
/*
* Attempt to test memory copy speeds. Use a buffer large enough to
gram.
Celeron 650 MHz (HP desktop) (DIMM)
16.16 MBytes/sec (copy)
Pentium III 550 MHz (Dell 2400) (DIMM)
25.90 MBytes/sec (copy)
Pentium 4 1.3 GHz / PC-800 RIMMs (Sony VAIO)
32.38 MBytes/sec (copy)
-Matt
Compile -O2,
/dev/null.
ad0: 58644MB [119150/16/63] at ata0-master UDMA100
-Matt
:> If one _truly_ needs the bandwidth of Rambus (which, IIRC, is
:> higher real-world latency than SDRAM), then how about having the
:> bus bandwidth to back it up?
:
:The higher rea
2000 bytes transferred in 1.471046 secs (1425619621 bytes/sec)
If I use lower block sizes the syscall overhead blows up the
performance (it gets lower rather then higher). So I figure I don't
have as much L2 as on your system.
-Matt
sec from main memory.
-Matt
/*
* NOTE: cc x.c -O2 -o x
*/
#include
#include
#include
#include
#include
#include
int deltausecs(struct timeval *tv1, struct timeval *tv2);
int
main(int ac, char **av)
{
int i;
int bytes;
double dtime;
struct tim
caled well
simply by adding memory or cpu. SCSI disks usually do better then IDE
in seek-limited situations. Higher-RPM disks can make a big difference
too.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-
ave to convert everything to 64 bit offsets all the way
through, especially with 500GB+ drives coming to market probably this
year sometime.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ions
to the number of hits/sec the webserver can handle.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
pipe (the
continuous) 'iostat ad0 10' output to a script and have the script pull
out the tps field and do something with it.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
on that you
need to track down and figure out.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
it with it.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
l with it again.
-Matt
:Sure, i386 code will run but the benchmarks seem to indicate that peak
:performance is heavily dependent on a good optimizing compiler.
:
:A query to the gcc mailing list returned no responses.
:
:Charles
To Unsubscribe: send mail to [EMAIL
.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:
:The people involved know.
:
Harrruummm. (Gong!)
Harrruummm. (Gong!)
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:
:On Mon, Mar 05, 2001 at 06:08:25PM -0800, Matt Dillon wrote:
:>
:> :I am trying to figure out corelation between Inactive and Free then.
:> :Inact would be unused ram right?
:> :Free would be what how much of Active is being used? So what you are
:> :saying is if there is to
Email: <[EMAIL PROTECTED]>
:WAND and NLANR MOATEmail: <[EMAIL PROTECTED]>
Is it possible that the user is over his inode quota rather then his
disk quota?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
out pages being
saved from destruction at the last moment.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
, and again those can be quite costly in small
quantities.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ycase, I think there'd be a problem here.
-Matt
:There's probably a way to include *some* of the libm functions (from
:/usr/src/lib/msun, since /usr/src/lib/libm is deprecated). However, this
:would require a considerable amount of Make
101 - 200 of 616 matches
Mail list logo
