All of lore.kernel.org
 help / color / mirror / Atom feed
From: "jds" <jds@soltis.cc>
To: Ryan Underwood <nemesis-lists@icequake.net>, reiserfs-list@namesys.com
Cc: openafs-info@openafs.org
Subject: Re: Problems with reiserfs when start OpenAFS 1.2.11-fc1 Segmentation fault with kernel 2.4.22-1.2174.nptl
Date: Wed, 3 Mar 2004 19:48:58 -0600	[thread overview]
Message-ID: <20040304014303.M64769@soltis.cc> (raw)
In-Reply-To: <20040304002804.GA5722@dbz.icequake.net>

Hi Ryan:

   Thanks for your help, the client openafs working again.

loop: loaded (max 8 devices)
Journalled Block Device driver loaded
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on loop(7,0), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Found sys_call_table at c033d9f0
Starting AFS cache scan...found 0 non-empty cache files (0%).

[root@angelinux root]# df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/hda2 reiserfs    12947988   2838624  10109364  22% /
/dev/hda3 reiserfs    10241116     33320  10207796   1% /home
none         tmpfs      382776         0    382776   0% /dev/shm
/var/afscache ext3       92659      4722     83153   6% /usr/vice/cache
AFS            afs     9000000         0   9000000   0% /afs

Regards.

Thanks at all people for help me ( Derek, Pete, Derrick )


---------- Original Message -----------
From: Ryan Underwood <nemesis-lists@icequake.net>
To: reiserfs-list@namesys.com
Sent: Wed, 3 Mar 2004 18:28:04 -0600
Subject: Re: Problems with reiserfs when start OpenAFS 1.2.11-fc1 Segmentation
fault with kernel 2.4.22-1.2174.nptl

> On Wed, Mar 03, 2004 at 07:00:06PM -0600, jds wrote:
> > Hi: Iam compile OpenAFS 1.2.11-fc1 with kernel 2.4.22-1.2174.nptl is OK
> > 
> > problems with reiserfs 3.6 and Fedora Core 1
> > the problems is when start the client AFS recive the messages:
> > 
> > [root@angelinux modload]# service afs start
> > Found libafs-2.4.22-1.2174.nptl-i686.o from SymTable... Loading...
> > Starting AFS services.....
> > /etc/init.d/afs: line 305:  3300 Segmentation fault      /usr/vice/etc/afsd
> > ${AFSD_OPTIONS}
> 
> You can't use the OpenAFS client on a ReiserFS filesystem.  It currently
> only supports ext2/ext3 filesystems.  If you only have reiser
> filesystems, just make a big empty file:
> # dd if=/dev/zero of=/var/afscache
> and make an ext2 filesystem on it:
> # mke2fs -F /var/afscache
> and loop-mount it wherever your afs cache needs to be.
> # mount -o loop,rw /var/afscache /usr/vice/cache
> 
> You can automate this in your fstab:
> /var/afscache /usr/vice/cache ext2 defaults,loop 0 0
> 
> -- 
> Ryan Underwood, <nemesis@icequake.net>
------- End of Original Message -------

  reply	other threads:[~2004-03-04  1:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040304005117.M99283@soltis.cc>
2004-03-04  1:00 ` Problems with reiserfs when start OpenAFS 1.2.11-fc1 Segmentation fault with kernel 2.4.22-1.2174.nptl jds
2004-03-04  0:28   ` Ryan Underwood
2004-03-04  1:48     ` jds [this message]
2004-03-04  3:46       ` Mike Fedyk
2004-03-04  7:18         ` Ryan Underwood
2004-03-04 23:07           ` [OpenAFS] " Dan Pritts
2004-03-05  1:40             ` Ryan Underwood

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=20040304014303.M64769@soltis.cc \
    --to=jds@soltis.cc \
    --cc=nemesis-lists@icequake.net \
    --cc=openafs-info@openafs.org \
    --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.