All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Krisztian Gy?rffy <krisztian.gyoerffy@telecare.at>
Cc: reiserfs-list@namesys.com
Subject: Re: problem with FS block_size
Date: Wed, 12 Jun 2002 14:22:47 +0400	[thread overview]
Message-ID: <20020612142247.A2093@namesys.com> (raw)
In-Reply-To: <004a01c211fa$6c92a040$1f79030a@connect.atwork.ent>

Hello!

On Wed, Jun 12, 2002 at 12:17:58PM +0200, Krisztian Gy?rffy wrote:

> I have a problem with my reiserFS. I have the following configuration running on my machine:
> - SMP 2.4.16-32 SuSE Linux kernel
> - software RAID1 with 2 disks
> - on top of the RAID I have LVM 1.0.1 (the /boot is exclusive, but the rest like /home, /, swap, /tmp, /opt, /usr in in the LVM)
> Everything is working fine with ext2fs and also with resierfs if I define block_size 4k. I downloaded from namesys.com the latest resierfs tools version reiserfsprogs-3.x.1b.tar.gz. But with that I still have the problem, if I define a block_size other that 4k, I eighter cannot mount the partition (filesystem type unknown), or at unmount I get segmentation fault. The first one I get with block_size 1k, the second with block_size 2k.
> Can you tell me what can be wrong there. Do I need some kernel pathes?

variable blocksize support was not merged in kernel yet.
I have a diff for 2.4.18-rc2, though. So if you need it, I can send it to you.
Note it is was not fully tested yet.

Bye,
    Oleg

      reply	other threads:[~2002-06-12 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12 10:17 problem with FS block_size Krisztian Györffy
2002-06-12 10:22 ` Oleg Drokin [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=20020612142247.A2093@namesys.com \
    --to=green@namesys.com \
    --cc=krisztian.gyoerffy@telecare.at \
    --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.