From: Alex Zarochentsev <zam@namesys.com>
To: Redeeman <redeeman@metanurb.dk>
Cc: Reiserfs Mailinglist <reiserfs-list@namesys.com>
Subject: Re: Reiser4 oopses...
Date: Wed, 5 Nov 2003 20:34:27 +0300 [thread overview]
Message-ID: <20031105173427.GG11516@backtop.namesys.com> (raw)
In-Reply-To: <1068053280.5195.2.camel@redeeman.linux.dk>
On Wed, Nov 05, 2003 at 06:28:01PM +0100, Redeeman wrote:
> :)
> now i see a debug message, i get to think about, is there a estimated
> date on how it will be ready? because there will be some time till i
> will get a new hd and that, and i would like to use reiser4 there :D
The oops is related to pseudo files, rest of reiser4 seems more stable.
> On Wed, 2003-11-05 at 18:21, Mike Benoit wrote:
> > While playing with pseudo files, doing things like creating "..uid" and
> > "..gid" files on a ext3 partition, then trying to copy them to a reiser4
> > partition, (using cp,mv, and tar) it seemed oopses were quite a common
> > occurance.
> >
> > Kernel Version: 2.6.0-test9 ... and latest Reiser4 snapshot.
--
Alex.
prev parent reply other threads:[~2003-11-05 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 17:21 Reiser4 oopses Mike Benoit
2003-11-05 17:28 ` Redeeman
2003-11-05 17:34 ` Alex Zarochentsev [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=20031105173427.GG11516@backtop.namesys.com \
--to=zam@namesys.com \
--cc=redeeman@metanurb.dk \
--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.