All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Reiserfs List <reiserfs-list@namesys.com>,
	Oleg Drokin <green@namesys.com>
Subject: reiser4 debugging status info
Date: Fri, 15 Aug 2003 19:38:19 +0400	[thread overview]
Message-ID: <3F3CFE6B.1010700@namesys.com> (raw)

Since some of you have started to play with reiser4, I think we should 
probably send a paragraph describing our debugging status every day or 
so until it becomes more stable.

So here is an excerpt from Oleg's timesheet that may interest those of you experimenting with reiser4.

+		 Experimenting with reiser4, found that tail conversion process
+		 changes modification time of a file converted which confuses
+		 bitkeeper and potenionally a lot more applications.
+		 Found one of the places and working with Nikita on fixing that
+		 one, but that did not help, looking for other code pieces that
+		 might lead to this, have not finished.
+		 Nikita committed some fixes that are supposedly important and
+		 should be enough to make new release (with 64 bit fixes and
+		 progs fixes), unfortunately new code crashes on fsx very
+		 quickly which makes it not suitable for release. Looking for
+		 cause, exchanging informations with Nikita.



-- 
Hans



             reply	other threads:[~2003-08-15 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 15:38 Hans Reiser [this message]
2003-08-15 15:56 ` reiser4 debugging status info Nikita Danilov
2003-08-15 16:08   ` Hans Reiser
2003-08-15 16:14     ` Nikita Danilov
2003-08-15 18:49       ` Mike Fedyk

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=3F3CFE6B.1010700@namesys.com \
    --to=reiser@namesys.com \
    --cc=green@namesys.com \
    --cc=reiserfs-list@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.