Hi there!
I have a strange problem and I hope you guys can help me.
We have several 4.6-RELEASE boxes running SSH, after connected for a
while (varies between 5 min. and an +-40) the connection dies. The SSH
on the server only writes out the following message: "fatal: Write
failed : permission
Rather than spamming the list with another 37K patch, I posted a
revised version at
http://csua.berkeley.edu/~das/swapoff.patch2
Thus spake Matthew Dillon <[EMAIL PROTECTED]>:
> The swap_pager_isswapped() function may not be doing
> a sufficient test:
[...]
> It is quite poss
Thus spake Nate Lawson <[EMAIL PROTECTED]>:
> Nice, thanks for doing this. How about some more accurate names for the
> userland routines instead of "this_is_swapoff" and "twiddle"?
Sure, suggest something and I'll change it. I shamelessly stole
'this_is_swapoff' from w / uptime, but you can bl
On Tue, Oct 08, 2002 at 09:18:21AM +, Riaal Domingues wrote:
> I have a strange problem and I hope you guys can help me.
>
> We have several 4.6-RELEASE boxes running SSH, after connected for a
> while (varies between 5 min. and an +-40) the connection dies. The SSH
> on the server only write
Giorgos Keramidas writes:
> On 2002-10-07 17:09, Ian Dowse <[EMAIL PROTECTED]> wrote:
> >
> > This is something I have been meaning to investigate for a while: [...]
> > Anyway, below is a proof-of-concept patch that does the basics, but
> > among other things, its logic for locating the ke
In message <[EMAIL PROTECTED]>, Andrew Gallatin
writes:
>gdbmods does an ugly thing which is incredibly useful. It assumes
>that the modules you want to debug are sitting in your kernel build
>pool. So what it does is extract the build directory from the kernel
>(using strings), and runs a find
:The code works fine in all of my tests, except that calling
:swapoff() when the system is under heavy paging load and has
:multiple swap devices sometimes leads to a few pages being missed
:by the scan. I think the problem is that some process allocates
:some swap and starts paging out just befo
Hi,
The mount(8) manpage doesn't mention it, so I assume that
there is no such thing as a "nomtime" option (analogous
to the "noatime" option) to prevent the mtimes of inodes
from being updated for each write access.
But maybe is there some other way to achieve that?
For example, updating of mt
:...
:detect when there is insufficient space. (I actually thought it
:was right the first time.) Can you see anything obviously wrong
:with my math?
:
:The code works fine in all of my tests, except that calling
:swapoff() when the system is under heavy paging load and has
:multiple swap devic
On Tue, Oct 08, 2002 at 07:17:59PM +0200, Oliver Fromme wrote:
> Hi,
>
> The mount(8) manpage doesn't mention it, so I assume that
> there is no such thing as a "nomtime" option (analogous
> to the "noatime" option) to prevent the mtimes of inodes
> from being updated for each write access.
>
>
Erik Trulsson <[EMAIL PROTECTED]> wrote:
> On Tue, Oct 08, 2002 at 07:17:59PM +0200, Oliver Fromme wrote:
> > [...]
> > For example, updating of mtimes is not neccessary on a
> > file system that contains a news spool, or the content of
> > a web cache, or similar transient data. Disabling t
On 8 Oct, Oliver Fromme wrote:
> I should have been more specific in my examples. Sorry.
>
> Think about INN with using cycbuffers (CNFS) when storing
> news articles (which is pretty standard on fullfeed news
> servers). Those cycbuffers are a bunch of large files.
> Their size never changes
:..
:>
:> Another example would be "oops", which is a very fast,
:> lightweight web proxy. It uses cyclic buffer files to
:> store the cached data, similar to INN's CNFS.
:>
:> I think in the above cases, a "nomtime" option would indeed
:> save some unnecessary overhead.
:
:Probably not much, e
Matthew Dillon <[EMAIL PROTECTED]> wrote:
>
> atime/mtime/ctime updates will collect in the in-memory inode
> and only be written to disk when the filesystem sync occurs once
> every 30-60 seconds or so. This is how it works with or without
> softupdates.
Is that also true
:Matthew Dillon <[EMAIL PROTECTED]> wrote:
: >
: > atime/mtime/ctime updates will collect in the in-memory inode
: > and only be written to disk when the filesystem sync occurs once
: > every 30-60 seconds or so. This is how it works with or without
: > softupdates.
:
:Is that
Oliver> (The reason why I'm asking: I am going to set up a new
Oliver> newsserver (INN) on a FreeBSD machine, where all data
Oliver> including the newsspool is stored on a NetApp Filer.)
For local INN storage you can avoid the mtime issue simply by using raw
disk partitions. For cycbu
Lyndon Nerenberg <[EMAIL PROTECTED]> wrote:
>
> Oliver> (The reason why I'm asking: I am going to set up a new
> Oliver> newsserver (INN) on a FreeBSD machine, where all data
> Oliver> including the newsspool is stored on a NetApp Filer.)
>
> For local INN storage you can avoid
17 matches
Mail list logo
