From: Hans Reiser <reiser@namesys.com>
To: ReiserFS List <reiserfs-list@namesys.com>
Cc: Clifford Beshers <clifford.beshers@lindows.com>,
Alexander Zarochentcev <zam@namesys.com>
Subject: known reiser4 bugs in latest auto-snapshot
Date: Thu, 17 Jun 2004 10:25:29 -0700 [thread overview]
Message-ID: <40D1D409.5030607@namesys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 45 bytes --]
this timesheet extract should be informative
[-- Attachment #2: [CVS] reiserfs --]
[-- Type: message/rfc822, Size: 2145 bytes --]
From: vs@thebsh.namesys.com
To: reiserfs-dev@namesys.com
Subject: [CVS] reiserfs
Date: Thu, 17 Jun 2004 19:00:57 ()
Message-ID: <20040617150057.24739.qmail@thebsh.namesys.com>
CVSROOT: /home/CVS
Module name: reiserfs
Repository: reiserfs/daily-reports/vs/
Changes by: vs@thebsh.namesys.com.(none) 04/06/17 19:00:57
Modified files:
reiserfs/daily-reports/vs/:
2004.06 1.12 -> 1.13
--------------[ DIFF ]----------------------------
Index: reiserfs/daily-reports/vs/2004.06
diff -u reiserfs/daily-reports/vs/2004.06:1.12 reiserfs/daily-reports/vs/2004.06:1.13
--- reiserfs/daily-reports/vs/2004.06:1.12 Wed Jun 16 19:03:05 2004
+++ reiserfs/daily-reports/vs/2004.06 Thu Jun 17 19:00:47 2004
@@ -118,3 +118,15 @@
trying to reproduce nfs + reiser4 + mozilla problem - not completed
trying to reproduce inode loading semaphore lockup - failed
END 2004.06.16:19.02 Wen TOTAL=3:35
+BEG 2004.06.17:11.29 Thu
+ stressing reiser4 used as root filesystem:
+ it has problems when it is full: mmap fails (due to unability to convert tail)
+ rm to free space locked, failed to find why
+ trying to find why nfs does not work (with Grev's help)
+ investigating iozone's lockup - not completed
+END 2004.06.17:15.04 Thu TOTAL=3:35
+BEG 2004.06.17:15.33 Thu
+ code cleanup
+ fighting with nfs (to try to reproduce mozilla + reiser4 + nfs corruption problem)
+ not completed
+END 2004.06.17:19.00 Thu TOTAL=3:27
--------------[ END DIFF ]------------------------
Log message:
vs's daily report for 17 june 2004
reply other threads:[~2004-06-17 17:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40D1D409.5030607@namesys.com \
--to=reiser@namesys.com \
--cc=clifford.beshers@lindows.com \
--cc=reiserfs-list@namesys.com \
--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.