Dear friends:
First, my thanks to all of you who responded to my problem with booting
up to FreeBSD 6. And thank you for explaining to me that the proper
forum for that is freebsd-questions. And that is what I will do from now
on. Thank you again.
Benjamin
Craig Boston wrote:
On Tue, Mar 07, 2006 at 09:04:02AM -0800, Freddie Cash wrote:
There's no need to copy files around. gmirror handles it all for you
behind the scenes. Just create the gmirror labels using the existing
disks/slices/partitions, then insert the second set of
I recently re-installed a local machine with FreeBSD 6.1 BETA 4, in
order to get around the SETFEATURES SET TRANSFER MODE problem I emailed
the list about earlier. I'm still having problems (slightly different
errors) when running with normal settings, so I've been running this box
in 'safe' mode.
Hello and thanks for the replay.
Peter Jeremy wrote:
On Mon, 2006-Mar-20 21:26:56 +0300, Anton Nikiforov wrote:
I have a FreeBSD box running 5.4-RELEASE-p8.
...
A week ago it was working just properly, but after adding more RAM (2GB
additional RAM, and i do not thing that this is
Hello I have the a Ferrari 4005 LMWI, the laptop comes with a bluetooth
mouse, did anyone made it work under freebsd?
And how ?
thank you in advanced
--
Mohamed M. Maher
___
freebsd-stable@freebsd.org mailing list
Maher Mohamed wrote:
Hello I have the a Ferrari 4005 LMWI, the laptop comes with a bluetooth
mouse, did anyone made it work under freebsd?
And how ?
There's a great bluetooth mailing list for FreeBSD, that this question
is better suited on, but anyway:
[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 care to read, what's
currently there, by
When I mount with large read and write sizes:
mount_nfs -r 65536 -w 65536 -U -ointr pandora:/backup /backup
it changes -- for the worse. Short time into it -- the file stops growing
according to the `ls -sl' run on the NFS server (pandora) at exactly 3200
FS blocks (the FS was created
:
: [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 care to read, what's
:currently
:When the client is in this state it remains quite usable except for the
:following:
:
: 1) Trying to start `systat 1 -vm' stalls ALL access to local disks,
: apparently -- no new programs can start, and the running ones
: can not access any data either; attempts to
вівторок 21 березень 2006 17:48, Matthew Dillon Ви написали:
:Actually, it does. The program tells it, that I don't care to read, what's
:currently there, by specifying the PROT_READ flag only.
That's an architectural flag. Very few architectures actually support
write-only memory
Hello All,
Anton Nikiforov wrote:
Hello and thanks for the replay.
Peter Jeremy wrote:
On Mon, 2006-Mar-20 21:26:56 +0300, Anton Nikiforov wrote:
I have a FreeBSD box running 5.4-RELEASE-p8.
...
A week ago it was working just properly, but after adding more RAM
(2GB additional
вівторок 21 березень 2006 17:56, Matthew Dillon Ви написали:
For UDP mounts, 65536 is too large (the UDP data length can
only be 65536 bytes. For that matter, the *IP* packet itself can
not exceed 65535 bytes. So 65536 will not work with a UDP mount.
Well, then the mount should
Hi!
On Tue, Mar 21, 2006 at 06:26:45PM -0500, Mikhail Teterin wrote:
The problem is about same with 32K and 16K packets. With 8K packets, the
thing
kind-of works (although trying to `systat -vm' still stalls disk access), but
the outgoing traffic is over 20Mb/s on average -- MUCH more,
вівторок 21 березень 2006 18:48, Patrick M. Hausen Ви написали:
On Tue, Mar 21, 2006 at 06:26:45PM -0500, Mikhail Teterin wrote:
The problem is about same with 32K and 16K packets. With 8K packets, the
thing kind-of works (although trying to `systat -vm' still stalls disk
access), but the
вівторок 21 березень 2006 18:48, Patrick M. Hausen Ви написали:
Are you using TCP or UDP for your NFS mounts?
Ok, I just tried tcp as follows:
mount_nfs -r 8192 -w 8192 -U -otcp,intr,tcp pandora:/backup /backup
(oops, twice :-)
The symptoms are largely the same. The file stopped
:I don't specify either, but the default is UDP, is not it?
Yes, the default is UDP.
: Now imagine a client that experiences this problem only
: sometimes. Modern hardware, but for some reason (network
: congestion?) some frames are still lost if sent back-to-back.
: (Realtek chipset on the
From Mikhail Teterin [EMAIL PROTECTED], Tue, Mar 21, 2006 at 06:58:01PM
-0500:
I'll try the TCP mount, workaround. If it helps, we can assume, our UDP NFS
is
broken for sustained high bandwidth writes :-(
What? I think you misunderstood. UDP NFS fairs poorly under
network congestion; it
вівторок 21 березень 2006 19:25, Matthew Dillon Ви написали:
If the program works over a local
filesystem but fails to produce data in the output file on an NFS
mount (but completes otherwise), then there is a bug in NFS somewhere.
If the problem is simply due to the program
: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
вівторок 21 березень 2006 20:09, Matthew Dillon Ви написали:
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 for that would be to ^Z the program once it gets into this state
and see if
вівторок 21 березень 2006 20:09, Matthew Dillon Ви написали:
If neither of those are an issue then I would guess that the problem
could be related to the NFSv3 2-phase commit protocol. A way to test
that would be to mount with NFSv2 and see if the problem still occurs.
Adding -2
вівторок 21 березень 2006 20:53, Matthew Dillon Ви написали:
Ah ha. That's the problem. I don't know why you are getting a write
error, but that is preventing the client from cleaning out the dirty
buffers. The number of dirty buffers continues to rise and the client
is just
Hi guys,
As part of testing how well some of our products work with latest
RELENG_6, I have make a new build and found that lot of important
services (for example PostgreSQL, Apache) doesn't start up (despite
having respective xxx_enable entries in /etc/rc.conf) when installed
from the
I have just realized that maybe the best approach to address this
problem would be not reverting the change in question, but making
find_local_scripts_new() more strict, so that only those local rc.d
scripts that have been explicitly marked by maintainer as fully
rc.d-safe are handled in a new
Hello friend !
You have just received a postcard from someone who cares about you!
This is a part of the message:
Hy there! It has been a long time since I haven't heared about you!
I've just found out about this service from Claire, a friend of mine
who also told me that...
Hi,
I work for a small company that makes radar systems for research
organisations and we use FreeBSD on the PCs for data acquisition and
processing. We have recently shifted to FreeBSD6/amd64 and one machine in
particular is exhibiting a strange problem.
The acquisition process is a Tcl
27 matches
Mail list logo
