From: Oleg Drokin <green@namesys.com>
To: Steve Pratt <slpratt@us.ibm.com>
Cc: reiserfs-list@namesys.com
Subject: Re: EVMS Reiser FSIM
Date: Fri, 31 May 2002 13:26:51 +0400 [thread overview]
Message-ID: <20020531132651.A9201@namesys.com> (raw)
In-Reply-To: <OFDCF5C080.996B2948-ON85256BC9.005E8AA0@pok.ibm.com>
Hello!
On Thu, May 30, 2002 at 12:14:03PM -0500, Steve Pratt wrote:
> >Yes, I know this.
> >I just want to confirm that the only way to look at it right now is to get
> >latest CVS version out of their cvs repository.
> At the moment CVS is the only place this is available. I wanted to give
> you guys a heads up that it was coming. We should be doing a version 1.1
> package in the next couple of weeks and the ReiserFS FSIM will be included
> in that.
Ok, I had a look into the CVS and I have few comments.
First is that mkfs output might exceed 10k buffer you have assigned to it,
and if messages that mkfs print would exceed 10k+pipe buffer size,
then mkfs process would block and you'd never get it to return
(and I do not see you have any way to exit on timeout or send a signal
to hung process on timeout).
Then I believe Hans asked you to display credits not only for reiserfsck, but
also for mkreiserfs. (and other reiserfs utilities if you run them).
Also just a note, you can return your own errors as negative exit codes
and pass utilities exit codes as it is.
So if the exit code of child process is bigger than 128, you can substract
this value from 255 and decide what error was caused that tool was not run.
Also you'd avoid a clash between EPERM vs FSCK_CORRECTED this way.
Ah, and please change recommended version of reiserfsprogs to 3.x.1b,
because 3.x.1a is not recommended in fact and have some known problems.
Thank you.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-31 9:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 17:14 EVMS Reiser FSIM Steve Pratt
2002-05-31 9:26 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 16:45 Steve Pratt
2002-06-04 15:02 Steve Pratt
2002-06-04 15:10 ` Oleg Drokin
2002-06-03 23:34 Steve Pratt
2002-06-03 21:03 Steve Pratt
2002-06-04 6:09 ` Oleg Drokin
2002-06-03 19:04 Steve Pratt
2002-06-03 19:36 ` Oleg Drokin
2002-05-31 17:40 Steve Pratt
2002-06-01 1:35 ` Andrew Clausen
2002-05-31 17:03 Steve Pratt
2002-05-31 17:28 ` Oleg Drokin
2002-06-03 16:00 ` Oleg Drokin
2002-05-30 19:02 Steve Pratt
2002-05-31 13:43 ` Andrew Clausen
2002-05-29 16:28 Steve Pratt
2002-05-30 7:37 ` Yury Umanets
2002-05-30 9:53 ` Andrew Clausen
2002-05-30 12:56 ` Hans Reiser
2002-05-30 23:50 ` Andrew Clausen
2002-05-29 13:46 Steve Pratt
2002-05-29 14:17 ` Yury Umanets
2002-05-30 5:09 ` Oleg Drokin
2002-05-30 5:32 ` Adrian Phillips
2002-05-30 5:54 ` Oleg Drokin
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=20020531132651.A9201@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=slpratt@us.ibm.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.