From: Chris Mason <mason@suse.com>
To: Pierre Etchemaite <petchema@concept-micro.com>
Cc: reiserfs-list@namesys.com
Subject: Re: allocator options, kernel 2.6.7
Date: Wed, 16 Jun 2004 19:38:53 -0400 [thread overview]
Message-ID: <1087429133.8002.15.camel@watt.suse.com> (raw)
In-Reply-To: <20040617012918.1cc93df9@rayanne>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
On Wed, 2004-06-16 at 19:29, Pierre Etchemaite wrote:
> Hi all,
>
> I've been using 2.6.5 kernel with data-logging, allocator options patch, and
>
> data=ordered,alloc=skip_busy:dirid_groups,packing_groups
>
> mount options for a while. So far so good.
>
>
> Now, two questions.
>
> 1. I came across this fix:
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.6/2.6.6-mm5/broken-out/reiserfs-block-allocator-should-not-inherit-packing-locality.patch
>
> Does that mean that I could have problem fixing some of my filesystems if
> they happened to need reiserfsck ?
>
There's a reiserfsprogs patch as well, which was sent to Vitaly. I've
attached it to this message.
> (From what I understand I can check if it's not too late already if
>
> /sbin/debugreiserfs -d /dev/xxxx |grep '^|.*SD'|sed 's/^.....//'|awk '$1==1'
>
> returns only one line, beginning with 1 2 ...)
>
>
> 2. kernel 2.6.7 seems to have data-logging patch applied (which is a very
> good news!), but not advanced allocator options patch. Is there a patch for
> 2.6.7, or would you recommend me forgetting about those options for now ?
> Allocator tweaks looks a bit more experimental than I thought.
It seemed best to keep the changes for 2.6.7 somewhat more limited. The
allocator patches are going through a big QA round at SUSE as well right
now, so any remaining problems should get ironed out very shortly.
-chris
[-- Attachment #2: reiserfsck-packing-groups.diff --]
[-- Type: text/x-patch, Size: 659 bytes --]
--- reiserfsck-3.6.17/fsck/pass0.c 2004-05-20 20:15:19.312305008 -0400
+++ reiserfsck-3.6.17.fix/fsck/pass0.c 2004-05-20 20:16:41.366830824 -0400
@@ -565,7 +565,8 @@
if (get_key_dirid (key) == 0 || get_key_objectid (key) == 0 || get_key_objectid (key) == 1 ||
get_key_dirid (key) == ~(__u32)0 || get_key_objectid (key) == ~(__u32)0 ||
get_key_dirid (key) == get_key_objectid (key) ||
- (get_key_dirid (key) == 1 && get_key_objectid (key) != 2) ||
+ /* the alloc=packing_groups used to allow dirid = 1
+ (get_key_dirid (key) == 1 && get_key_objectid (key) != 2) || */
(get_key_dirid (key) != 1 && get_key_objectid (key) == 2) )
return 1;
next prev parent reply other threads:[~2004-06-16 23:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 23:29 allocator options, kernel 2.6.7 Pierre Etchemaite
2004-06-16 23:38 ` Chris Mason [this message]
2004-06-17 0:05 ` Pierre Etchemaite
2004-06-17 5:31 ` Mike Benoit
2004-06-17 9:48 ` Dieter Nützel
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=1087429133.8002.15.camel@watt.suse.com \
--to=mason@suse.com \
--cc=petchema@concept-micro.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.