All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: sander@humilis.net
Cc: Alex Zarochentsev <zam@namesys.com>,
	reiserfs-list@namesys.com, "E. Gryaznova" <grev@namesys.com>
Subject: Re: www.namesys.com down
Date: Thu, 24 Jun 2004 09:13:02 -0700	[thread overview]
Message-ID: <40DAFD8E.7010304@namesys.com> (raw)
In-Reply-To: <20040624144725.GA26097@favonius>

Sander wrote:

>Hi Alex,
>
>Alex Zarochentsev wrote (ao):
>  
>
>>On Thu, Jun 24, 2004 at 11:02:31AM +0200, Sander wrote:
>>    
>>
>>>I notice www.namesys.com is down for quite some time now. At first
>>>it was not pingable, but now just the webserver refuses to 'serve
>>>the web'. Is this due to the migration to reiserfs4?
>>>      
>>>
>>Yes. Yesterday we resolved apache2/reiser4 issue. Now the server is
>>reconfigured again.
>>    
>>
More precisely, it seems that all of our regression tests don't test 
sendfile.  We need to fix that.  grev, please look into it.

>
>Thank you for your answer.
>
>When do you think reiser4 is able to serve www.namesys.com again? I
>would like to try it for my own webserver, but if Namesys doesn't dare
>to, then I don't for sure ;-)
>
>Is there a list of know reiser4 issues online? A quick search on
>www.namesys.com didn't reveal it.
>  
>
There are none remaining, except performance drop due to ent threads 
needing to be optimized if we use them (and ent threads are needed for 
good iozone performance).

>        Kind regards, Sander
>
>
>  
>


      reply	other threads:[~2004-06-24 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24  9:02 www.namesys.com down Sander
2004-06-24  9:12 ` Alex Zarochentsev
2004-06-24 14:47   ` Sander
2004-06-24 16:13     ` Hans Reiser [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40DAFD8E.7010304@namesys.com \
    --to=reiser@namesys.com \
    --cc=grev@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=sander@humilis.net \
    --cc=zam@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.