All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Clusterfs.COM>
To: Hans Reiser <reiser@namesys.com>
Cc: David Dabbs <david@dabbs.net>,
	'ReiserFS List' <reiserfs-list@namesys.com>,
	Alexander Zarochentcev <zam@namesys.com>,
	"E. Gryaznova" <grev@namesys.com>
Subject: Re: Was able to reproduce "cp: cannot stat file.x: Input/output error"
Date: Mon, 9 Aug 2004 19:13:28 +0400	[thread overview]
Message-ID: <16663.38040.898214.643240@laputa.namesys.com> (raw)
In-Reply-To: <41166C28.6030402@namesys.com>

Hans Reiser writes:
 > David Dabbs wrote:
 > 
 > >  
 > >
 > >>-----Original Message-----
 > >>From: Hans Reiser [mailto:reiser@namesys.com]
 > >>Sent: Saturday, August 07, 2004 11:18 PM
 > >>To: David Dabbs
 > >>Subject: Re: Was able to reproduce "cp: cannot stat file.x: Input/output
 > >>error"
 > >>
 > >>    
 > >>
 > >
 > >  
 > >
 > >>How about, code was X, now it is Y, with just the relevant parts of the
 > >>code cited?
 > >>    
 > >>
 > >
 > >Probably the most significant change to mongo sources is how it generates
 > >file names. Mongo.pl had a hard coded value of 6 for the "max_fname"
 > >parameter passed to reiser_fract_tree. I made this a parameter one can
 > >specify on the mongo command line. I passed it a value of 23.
 > >  
 > >
 > most filenames are small.  We have an optimization in reiser4 that 
 > assumes filenames are less than 15 characters, which most of them are.

With large keys (which is the default) up to 23 characters are
embedded into key.

[...]

Nikita.

  parent reply	other threads:[~2004-08-09 15:13 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4115A979.5090002@namesys.com>
2004-08-08  7:07 ` Was able to reproduce "cp: cannot stat file.x: Input/output error" David Dabbs
2004-08-08 18:08   ` Hans Reiser
2004-08-08 19:09     ` David Dabbs
2004-08-09  6:17       ` Hans Reiser
2004-08-08 21:40         ` David Dabbs
2004-08-09  0:01           ` Hans Reiser
2004-08-09  1:55             ` David Dabbs
2004-08-09 17:43               ` Hans Reiser
2004-08-09 18:32                 ` David Dabbs
2004-08-09  2:38             ` David Dabbs
2004-08-09 17:59               ` Alex Zarochentsev
2004-08-09 18:22                 ` David Dabbs
2004-08-09 18:42                   ` Alex Zarochentsev
2004-08-09 15:13     ` Nikita Danilov [this message]
2004-08-09 17:48       ` Hans Reiser
     [not found] <411944EF.7000504@namesys.com>
2004-08-10 22:05 ` David Dabbs
     [not found] <20040810205450.GU9811@backtop.namesys.com>
2004-08-10 21:06 ` David Dabbs
2004-08-10 21:06   ` Alex Zarochentsev
2004-08-10 21:19     ` David Dabbs
2004-08-11 10:03       ` Vladimir V. Saveliev
2004-08-10 21:26     ` David Dabbs
2004-08-06  6:53 David Dabbs
2004-08-06 15:51 ` Vladimir V. Saveliev
2004-08-06 17:10   ` Philippe Gramoullé
2004-08-06 17:39     ` Vladimir V. Saveliev
2004-08-06 19:06       ` Philippe Gramoullé
2004-08-07  4:14       ` Hans Reiser
2004-08-06 17:46     ` David Dabbs
2004-08-06 19:11       ` Philippe Gramoullé
2004-08-07  4:15       ` Hans Reiser
2004-08-07  6:46         ` David Dabbs
2004-08-07  7:49           ` Hans Reiser
2004-08-08  2:54             ` David Dabbs
2004-08-10  3:21             ` Valdis.Kletnieks
2004-08-10  8:31               ` Hans Reiser
2004-08-10 15:41                 ` Valdis.Kletnieks
2004-08-10  9:20               ` Alex Zarochentsev
2004-08-10 17:35                 ` Hans Reiser
2004-08-10 17:42                   ` David Dabbs
2004-08-10 17:46                     ` Hans Reiser
2004-08-10 18:05                   ` Alex Zarochentsev
2004-08-10 19:55                     ` Hans Reiser
2004-08-10 20:41                       ` Alex Zarochentsev
2004-08-06 17:51     ` Alex Zarochentsev
2004-08-06 19:10       ` Philippe Gramoullé
  -- strict thread matches above, loose matches on Subject: below --
2004-08-06  4:54 David Dabbs
2004-08-06  7:31 ` mjt

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=16663.38040.898214.643240@laputa.namesys.com \
    --to=nikita@clusterfs.com \
    --cc=david@dabbs.net \
    --cc=grev@namesys.com \
    --cc=reiser@namesys.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.