All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Cris Rhea <crhea@mayo.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: Two possible bugs in V3 ReiserFS and 2.4.31 kernel??
Date: Tue, 23 Aug 2005 15:04:42 +0400	[thread overview]
Message-ID: <430B02CA.5050209@namesys.com> (raw)
In-Reply-To: <20050822201535.GA15324@kaizen.mayo.edu>

Hello

Cris Rhea wrote:
> Background:
> 
> Dell 6600 (4 processor, 8GB memory) with RHAS3 loaded.
> Email product vendor suggests using ReiserFS V3 on mail spool directory
> for speed (many files in one directory).
> 
> Since RedHat does not support/include ReiserFS in their kernels, download
> and build the latest 2.4 kernel:
> 
> 	linux-2.4.31.tar.gz (ftp.kernel.org)
> 
>>From my reading, there are NO patches for ReiserFS...
> 
> Take current kernel config (RedHat's kernel-2.4.21-i686-smp.config) and 
> use it for the base for the 2.4.31 kernel (make oldconfig). Take defaults 
> (mostly "N") for all new features.  Reiserfs is a module. 
> 
> Download, compile, and install reiserfsprogs-3.6.19.tar.gz.
> 
> Upon reboot, reiserfs shows up in lsmod....
> 
> mkreiserfs -b 2048 /dev/sdc1  (sdc1 is a RAID-5 hardware LUN on the Dell
>                               PERC controller. Only one partition defined 
>                               [entire disk] as type 83.)
> Command completes successfully.
> 
> reiserfsck /dev/sdc1 also works successfully....
> 
> Mount via fstab or via: mount -t reiserfs /dev/sdc1 /var/spool/MHS1
> fails with:
> 
> mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
>        or too many mounted file systems
> 
> Running the mkreiserfs without the "-b 2048" works fine (correctly mounts).
> 

Yes, please use always default block size.

> Second problem.... if one labels the filesystem during build
> (mkreiserfs -l "/var/spool/MHS1" /dev/sdc1), this fails to mount if you
> use the "LABEL=/var/spool/MHS1" option in /etc/fstab.  This is supposed to
> work on 3.6 per the FAQ.
> 

this works perfectly on 2.6.13-rc6-mm1. And probably on earlier 2.6 kernels.

> I didn't find much on the 'net other than patches/problems for early 
> 2.4 kernels. 
> 
> I'm having a hard time believing nobody has ever tried "-b 2048" on 
> V3 ReiserFS previously.... must be something hosed in the latest
> kernel.....

This is known reiserfs problem: no block sizes other than default one

      reply	other threads:[~2005-08-23 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 20:15 Two possible bugs in V3 ReiserFS and 2.4.31 kernel?? Cris Rhea
2005-08-23 11:04 ` Vladimir V. Saveliev [this message]

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=430B02CA.5050209@namesys.com \
    --to=vs@namesys.com \
    --cc=crhea@mayo.edu \
    --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.