public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: erik@hensema.net
Cc: linux-kernel@vger.kernel.org, Nikita Danilov <god@laputa.namesys.com>
Subject: Re: First impressions of reiserfs4
Date: Sat, 30 Aug 2003 21:06:14 +0400	[thread overview]
Message-ID: <3F50D986.6080707@namesys.com> (raw)
In-Reply-To: <slrnbl12sv.i4g.erik@bender.home.hensema.net>

Erik Hensema wrote:

>Currently I'm testing reiserfs4 on my otherwise vanilla 2.6.0-test4
>machine.
>
>At first I tried building reiser4 as a module. The kernel failed to link
>due to an unresolved symbol: sys_reiser4
>
compile without sys_reiser4 and not as a module, the config is fixed in 
what will be the next snapshot

>I tried commenting sys_reiser4 out from entry.S. Now the kernel linked
>fine.
>
>However, I can't insert the module due to unexported symbols:
>
>reiser4: Unknown symbol balance_dirty_pages
>reiser4: Unknown symbol max_sane_readahead
>reiser4: Unknown symbol generic_sync_sb_inodes
>reiser4: Unknown symbol truncate_mapping_pages_range
>reiser4: Unknown symbol wakeup_kswapd
>reiser4: Unknown symbol balance_dirty_pages_ratelimited
>reiser4: Unknown symbol inodes_stat
>reiser4: Unknown symbol nr_free_pagecache_pages
>reiser4: Unknown symbol destroy_inode
>
>So, I tried linking reiser4 directly into the kernel. No problems there.
>
>As we speak I'm building Mozilla Firebird from source of a 20 GB reiser4
>partition. If something interesting comes up, this list will be the first
>to know :-)
>
>I've currently got only one small problem: df can't handle the data from
>the kernel it seems. I also got this problem on NFS mounted partitions:
>
fixed in what will be the next snapshot

>
>df: `/reiser4': Value too large for defined data type
>df: `/home': Value too large for defined data type
>
>  
>
thanks for your patience.

nikita, when are you releasing the next snapshot, with the improved 
performance and bug fixes

-- 
Hans



  reply	other threads:[~2003-08-30 17:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-30 11:33 First impressions of reiserfs4 Erik Hensema
2003-08-30 17:06 ` Hans Reiser [this message]
2003-08-31 17:14   ` Rogier Wolff
2003-09-08  8:12     ` Oleg Drokin
2003-09-08  8:56       ` Rogier Wolff
2003-09-08  9:08         ` Oleg Drokin
2003-09-08  9:33           ` Rogier Wolff
2003-09-08  9:48             ` Oleg Drokin
2003-09-08 10:05               ` Rogier Wolff
2003-09-08 10:17                 ` Oleg Drokin
2003-09-08 12:59                   ` Herbert Poetzl
2003-09-08 22:24                   ` Mike Fedyk
2003-09-09  7:04                     ` Oleg Drokin
2003-09-09 19:10                       ` Mike Fedyk
2003-09-11 10:29                         ` Oleg Drokin
2003-09-11 17:15                           ` Reiser3/4 & Ext2/3 was: " Mike Fedyk
2003-09-11 17:27                             ` Oleg Drokin
2003-09-11 22:50                               ` Rogier Wolff
2003-09-12  1:20                                 ` Bernd Eckenfels
2003-09-12  4:48                                   ` Mike Fedyk
2003-10-01 21:06                                     ` Bernd Eckenfels
2003-10-02  6:36                                       ` Hans Reiser
2003-09-12  1:17                             ` Bernd Eckenfels
2003-09-08 20:11       ` Andreas Dilger

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=3F50D986.6080707@namesys.com \
    --to=reiser@namesys.com \
    --cc=erik@hensema.net \
    --cc=god@laputa.namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox