Hello!
After another reboot, I started getting the message in subject and thus
have lost my network connection.
The card used to be identified as:
sk0: Marvell Semiconductor, Inc. Yukon on skc0
[]
I initially rebooted to add RAM to the machine, but have since tried to
take
If this drive doesn't support tagged-queueing, is the write cache
disabled? I get that sort of performance from a (PATA) disk with
the cache disabled (hw.ata.wc=0 in loader.conf)
No, just checked -- the hw.ata.wc is set to 1. Is there anything else to look
at?
According to smartctl, the
Indeed, 55C is way to high for 24/7 usage, and it might be that the
drive is choking on it and barely is able to compensate..
The reads are pretty quick... I'd like to be able to spin it down, but
ataidle is broken :-(
What does SMART say ? any unusual like high correction rates or
Ask the maintainer to get it [ataidle -mi] fixed, but be warned experience
says it might hose your data...
The maintainer did not break it. An incompatible change to the API did :) You
are, probably, in the best position to show us, how the new API should be
used.
Now, you say read speed is
Look in smartmontools I provided patches for that, its not rocket
science you know...
This attitude -- on top of the API change itself -- is not really encouraging
for ISVs, you know :-)
You need to find out what the transfer rates are for the RAW disk, ie
by doing a dd from /dev/zero
Hmm, that does sound as problems with that disk, or maybe disk vs
diskcontroller. Any chance you could try the disk on something else ?
I'll try...
One other thing, how much mem do you have in there ? more than 4G and
bounce buffering might get into the picture ruining the transfer
A few years ago, there was a project making a filesystem, where a file's name
will simply be its inode number. It was intended to save on the name-to-inode
lookups of a regular filesystem, for applications like Squid, which keep file
names in some sort of a database already.
Does anyone know,
On Thu, Mar 10, 2005 at 12:53:20PM -0500, Mikhail Teterin wrote:
A few years ago, there was a project making a filesystem, where a file's
name will simply be its inode number. It was intended to save on the
name-to-inode lookups of a regular filesystem, for applications like
Squid, which
Nullfs works better than unionfs. Unionfs worked well in 4.X.
What about the `union' option to regular mounts? Is that safe to use?
[...]
Last I checked, it [mount -ounion -mi] was very broken, but I'm not sure.
BTW, how is unionfs different from nullfs with the union option?
mount
Hello!
The respected manual contain dire warnings, but the Google search suggests,
the situation is not *that* gloomy.
For example, according to http://kerneltrap.org/node/652 , nullfs was used on
Bento-cluster two years ago in 2003.
Is anybody working on this file-systems? Any plans,
Hello!
A Google search for the Subject brought up a recent thread on this list.
We have an amd64 system running 5.3-BETA5, with almost-working amdpm0:
amdpm0: AMD 756/766/768/8111 Power Management Controller port
0xe0-0xff,0xb400-0xb41f irq 19 at device 7.2 on pci0
amdpm0: could not map i/o space
David Schwartz once wrote:
The man page is correct and the implementation is correct.
Several people, said the man pages are broken:
Bruce Evans on Dec 28:
If timeout is a non-nil pointer, it specifies
a maximum interval to wait for the selection
Dan Nelson once stated:
=In the last episode (Jan 23), Mikhail Teterin said:
= =FreeBSD is clearly not capable of hard real-time. If I remember
= =correctly, neither are any of the operating systems from which you
= =quoted man pages. That makes *all* of those man pages inaccurate
Warner Losh once stated:
=In message [EMAIL PROTECTED] Mikhail Teterin writes:
=: Where does it guarantee that? Man-pages say, it is guaranteed to
=: sleep no MORE then the timeout, not less. Is there some other
=: specification, that's different from the man-pages
Andre Albsmeier once wrote:
Before running soffice for the first time -- apply the trick
described by Andre Albsmeier on
http://www.freebsd.org/cgi/getmsg.cgi?fetch=432982+436209+/usr/local/www/db/text/1998/freebsd-hackers/19980628.freebsd-hackers
to the freshly installed
Marcel Moolenaar once wrote:
I don't think this one is needed anymore ?!?
It is. Without it, soffice keeps bringing up setup over and over
instead of just starting the damn office.
What is everybody doing? I run SO5.1 OOTB. AFAICT, there's absolutely
no need for this kind
Andre Albsmeier once wrote:
Before running soffice for the first time -- apply the trick
described by Andre Albsmeier on
http://www.freebsd.org/cgi/getmsg.cgi?fetch=432982+436209+/usr/local/www/db/text/1998/freebsd-hackers/19980628.freebsd-hackers
to the freshly installed
Marcel Moolenaar once wrote:
I don't think this one is needed anymore ?!?
It is. Without it, soffice keeps bringing up setup over and over
instead of just starting the damn office.
What is everybody doing? I run SO5.1 OOTB. AFAICT, there's absolutely
no need for this kind of
With relatively small amount of hackery, the StarOffice51 for Linux can
be forced to run on FreeBSD. Both, the setup and the office itself.
To run setup, you need to unzip the setup.zip (with the -L flag) and
make all the libraries there known to the ld-linux.so. (I just added a
new
With relatively small amount of hackery, the StarOffice51 for Linux can
be forced to run on FreeBSD. Both, the setup and the office itself.
To run setup, you need to unzip the setup.zip (with the -L flag) and
make all the libraries there known to the ld-linux.so. (I just added a
new
-8.2 released two weeks ago), knowing someone
else is making the so51 happening.
-mi
On Wed, 01 September 1999, Will Andrews wrote:
On 01-Sep-99 Mikhail Teterin wrote:
If Sun doesn't release the sources this month, I'll submit a port...
I was going to update the source
21 matches
Mail list logo
