All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Uhrain <buhrain@rosettastone.com>
To: reiserfs-list@namesys.com
Subject: New Reiser4 patch
Date: Fri, 17 Mar 2006 10:25:35 +0000	[thread overview]
Message-ID: <441A8E9F.4030602@rosettastone.com> (raw)

Hi,

I just noticed that a Reiser4 patch for kernel 2.6.14.6 was posted on 
ftp.namesys.com yesterday, and I was wondering what changes (if any) 
there are to Reiser4 itself between that patch and the 2.6.15 patch that 
was released two months ago?  Does it fix the issue with the periodic 
(temporary) system freezes during I think background flushes that was 
discussed previously on the list?  And out of curiosity, is there a 
specific technical reason why the patch is for 2.6.14.6 instead of one 
of the 2.6.15 source trees?

Sorry for the barrage of questions as my first post to this list.. :D  I 
use Reiser4 as the root filesystem on all four of my systems (two 
Athlon64 laptops and a dual-core Athlon64 desktop, both using x86-64 
kernels, and a dual processor Alpha).  And I must say, keep up the good 
work!  Except for the pausing issue with the (older) 2.6.14 and 2.6.15 
patches--which I've not even noticed on my dual-core system--and the 
mmap issue (only a problem with VMware, which will hard lock a system), 
the filesystem has worked superbly for me.  I've been using it for 
probably a year or more now as my root FS and have not had any data loss 
or corruptions.  I've even been using it on my Alpha system since I got 
it about a month ago (a CS20 with dual 833MHz EV67 processors) without 
any problems--all of the system software from glibc through Xorg have 
been built at least twice on it without troubles.

Thanks,
Brian


P.S.  If you want any more information on the VMware issue, I can see if 
it still does it on one of my home systems, and try to grab kernel 
messages via serial console.  I only encountered it when I first set up 
my dual-core system at work because I made everything Reiser4, while on 
my laptops my home directory is in a separate Reiser3 partition.  My 
workaround was to put the VMware virtual disks on their own Reiserfs 
partition.

             reply	other threads:[~2006-03-17 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 10:25 Brian Uhrain [this message]
2006-03-17 10:35 ` Announcements? (was: Re: New Reiser4 patch) Raymond A. Meijer
2006-03-19  2:06   ` Announcements? Joe Feise
2006-03-17 12:46 ` New Reiser4 patch Vladimir V. Saveliev
2006-03-18 11:52   ` Lexington Luthor
2006-03-19 17:11   ` Brian Uhrain

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=441A8E9F.4030602@rosettastone.com \
    --to=buhrain@rosettastone.com \
    --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.