Linux ReiserFS filesystem (obsolete)
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Jaroslav Fojtik <JaFojtik@seznam.cz>
Cc: Jeff Mahoney <jeffm@suse.com>,
	Reiserfs mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: Re4: Reiserfs3 is crashing - where/whom to report?
Date: Tue, 20 Jan 2009 21:19:03 +0300	[thread overview]
Message-ID: <49761597.1060305@gmail.com> (raw)
In-Reply-To: <49760EC3.25886.AFADA@JaFojtik.seznam.cz>

Jaroslav Fojtik wrote:
> Dear Jeff Mahoney,
>
>   
>>> Ok, please, have the 2.6.24.7 kernel and reiserfsprogs-3.6.21
>>> to format a partition:
>>> http://www.kernel.org/pub/linux/utils/fs/reiserfs/reiserfsprogs-3.6.21.tar.gz
>>> Catch all kernel messages and describe steps to reproduce the crash.
>>>       
>> Since reiserfsprogs 3.6.21 doesn't support block sizes < 4k, he'll be
>> unable to.
>>     
>
> I would like to ask you - I have made windiff 3.6.19 and 3.6.21 and I have noted
> several changes.
>
> I can comment this piece of code if you really want to catch and fix 
> a problem found:
>     } else if (blocksize < 4096) {
>         reiserfs_warning (stderr, "Block sizes smaller than 4k "
> 			  "are not supported.\n");
> 	return 0;
>     }
>
> I do not know why these block sizes has been disabled - stability? speed?
> Overflowing block count?
>   
http://bugzilla.kernel.org/show_bug.cgi?id=9108

Reiserfs has never worked properly with small blocksizes, and it was
unpleasant surprise when I saw that it is enabled again in
reiserfsprogs-3.6.19.

IMHO there is no chances to make reiserfs work with 512K blocks.
Other cases should be carefully debugged. Put in longterm todo.

Edward.

  reply	other threads:[~2009-01-20 18:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49750FC1.23700.2C929@JaFojtik.seznam.cz>
2009-01-20  0:20 ` Reiserfs3 is crashing - where/whom to report? Edward Shishkin
2009-01-20  4:49   ` Jeff Mahoney
2009-01-20  9:09     ` Re2: " Jaroslav Fojtik
     [not found]   ` <49759410.20384.D37CA@JaFojtik.seznam.cz>
2009-01-20 10:45     ` Edward Shishkin
2009-01-20 14:54       ` Jeff Mahoney
2009-01-20 17:49         ` Re4: " Jaroslav Fojtik
2009-01-20 18:19           ` Edward Shishkin [this message]
2009-01-20 18:49             ` Re6: " Jaroslav Fojtik
2009-01-20 18:54               ` Edward Shishkin
2009-01-20 21:20                 ` Re8: " Jaroslav Fojtik
2009-01-20 23:07                   ` Jeff Mahoney
2009-01-21 19:34                     ` Re10: " Jaroslav Fojtik
2009-01-21 19:25                       ` Jeff Mahoney
2009-01-27 21:30                         ` Re12: " Jaroslav Fojtik

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=49761597.1060305@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=JaFojtik@seznam.cz \
    --cc=jeffm@suse.com \
    --cc=reiserfs-devel@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