vs, please review and respond in 2 weeks. (vs is sick at the moment)
Thanks Adrian,
Hans
Adrian Bunk wrote:
>This patch contains possible cleanups including the following:
>- make needlessly global code static
>- plugin/compress/minilzo.c: many cleanups
>- remove or #if 0 the following unu
Bug reports that are hardware failures masquerading as reiserfs bugs
dominate our mailing list. We also get bug reports from users with
versions that are prior to 2.4.4. We are now working on making the code
more likely to identify a hardware failure as a hardware failure
(without killing perfor
Dirk Mueller wrote:
>
> Now consider a good amount of fragmentation because those files get created
> over time (weeks, months etc). and you quickly degenerade to a scanning
> speed of maybe 10-20 files per second (Athlon 800, IBM 60GB HD with roughly
> 35MB/s linear read). It was that horrible t
Alan Cox wrote:
> > that reiserfs has had lots of bugs, and is marked as experimental in kernel
> > 2.4.4. Not to mention that the people of RH discourage there users from using
> > it.
>
> At the time Red Hat 7.1 was mastered Reiserfs was not stable. The reiserfs in
> the RH kernel has some of t
Daniel Podlejski wrote:
> In linux-kernel, [EMAIL PROTECTED] wrote:
> : We are waiting for a server with dual PIII, RAID 1,0 and 5 18Gb scsi disks to
> : come so we can change our proxy server, that will run on Linux with Squid.
> : One disk will go inside (I think?) and the other 4 on a tower
I would encourage all of you to consider using a fractal fileset generator such as
reiserfs_fract_tree.c such as we use for mongo.pl which we use for internal
benchmarking. You can get a copy at www.namesys.com in the benchmarking section,
and then tune it as suits your needs. I think that one n
Matthias Andree wrote:
>
> If you're deploying a cache partition such as /var/squid (possibly
> having log files in another /var/log partition on another disk drive),
> what's the point about not running (e. g.) mke2fs and squid -z on boot,
> as well as mounting the system partitions (/usr) read
Tony Hoyle wrote:
> Matthias Andree wrote:
>
> > ext3fs has never given me any problems, but I did not have it in
> > production use where I discovered major ReiserFS <-> kNFSd
> > incompatibilities. ext3 has a 0.0.x version number which suggests it's
> > not meant for production use.
>
> Hmm...
Tony Hoyle wrote:
> Matthias Andree wrote:
>
> > You're not getting data loss, but access denied, when hitting
> > incompatibilities, and it looks like it hits 2.2 hard while 2.4 is less
> > of a problem. Please search the reiserfs list archives for details.
> > vs-13048 is a good search term, I
"Henning P. Schmiedehausen" wrote:
> Chris Mason <[EMAIL PROTECTED]> writes:
>
> >It requires explicit changes to each filesystem that wants to work over
> >NFS, and is a somewhat large change.
>
> Come on, we got zerocopy TCP pushed into a stable kernel release with
> the words "get over it".
>
Alan Cox wrote:
> > I think with the growing acceptance of ReiserFS in the Linux
> > community, it is tiresome to have to apply a patch again and again
> > just to get working NFS. 2.2 NFS horrors all over again.
>
> The zero copy patches were basically self contained and tested for 6 months.
> T
Alan Cox wrote:
> > Are you referring to Neil Brown's nfs operations patch as being as ugly as
> > hell, or something else? Just want to understand what you are saying before
> > arguing.
>
> Andi has sent me some stuff to look at. He listed four implementations and I've
> only seen two of t
Steve Lord wrote:
> >
> > XFS is very fast most of the time (deleting a file is so slow its like us
> > ing
> > old BSD systems). Im not familiar enough with its behaviour under Linux yet.
>
> Hmm, I just removed 2.2 Gbytes of data in 3 files in 37 seconds (14.4
> seconds system time), no
"Albert D. Cahalan" wrote:
> Hans Reiser writes:
>
> > Tell us what to code for, and so long as it doesn't involve looking
> > up files by their 32 bit inode numbers we'll probably be happy to
> > code to it. The Neil Brown stuff is already code
We haven't been sending much email out, but we have been working away.
We just finished the VFS work, and will send a patch out on Monday.
akpm asked for a bullet list of things suggested on lkml as issues for
inclusion.
There are some things that I would like akpm to confirm represent the
off
Chris Shoemaker wrote:
>On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote:
>
>
>>If we lose every remaining point of this list, we can generate a patch
>>in a few days, because the VFS work was the only substantive (in coding
>>hours) task, and it is done
Christoph Hellwig wrote:
> 6. remove type safe lists and type safe hash queues.
>
>> not done, it is not clear that the person asking for this represents a
>> unified consensus of lkml. Other persons instead asked that it just be
>> moved out of reiser4 code into the generic kernel code, whic
Andrew Morton wrote:
>
>
>
>>1. pseudo files or "" files
>>
>>
>>
>
>
>
>> disabled. It remains a point of (extraordinary) contention as to
>>whether it can be fixed, we want to keep the code around until we can
>>devote proper resources into proving it can be (or until we fail to pr
101 - 118 of 118 matches
Mail list logo
