From: Oleg Drokin <green@namesys.com>
To: Francois-Rene Rideau <fare@tunes.org>
Cc: reiserfs-list@namesys.com
Subject: Re: mkreiserfs -s 1024 makes unmountable partitions
Date: Mon, 27 Jan 2003 09:59:57 +0300 [thread overview]
Message-ID: <20030127095957.A22720@namesys.com> (raw)
In-Reply-To: <20030126181816.GA1274@Kadath>
Hello!
On Sun, Jan 26, 2003 at 07:18:16PM +0100, Francois-Rene Rideau wrote:
> Hi! No hard disk crash today (I'm just disabling the DMA )-" )
> However, I've tried to make small reiserfs partitions,
> and was annoyed at the journal taking a significant size of the disk:
> 32MB is 50% of my 64MB /boot partition, and 40% of the whole
> of my server's 80MB harddisk.
> I saw that mkreiserfs had an option -s to select the size of the journal,
> and tried to use it to make a 4MB journal:
> mkreiserfs -s 1024 /dev/hdc1
> However, whereas mkreiserfs didn't complain, the resulting partition
> was unmountable by linux. In the syslogs, the kernel complains:
> read_super_block: can't find a reiserfs filesystem on (dev 16:01, block 128, size 512)
> read_super_block: can't find a reiserfs filesystem on (dev 16:01, block 16, size 512)
You need journal relocation patches from Chris Mason.
ftp://ftp.suse.com/pub/people/mason/patches/datalogging
> I there a way to make a reiserfs partition with a small journal?
Sure. You just did it. ;)
Not you need in-kernel support to be able to mount it.
Ir You can use 2.5 kernels (note these are not recommended for productional environment
of course)
> Would a small kernel patch do it?
Sure.
> In any case, I think that it is a bug that mkreiserfs doesn't check
> the consistency of its parameters with what the kernel is able to handle.
No, that's not a bug. mkreiserfs cannot know if you are just making a filesystem
and planning to reboot into proper kernel later (or even move the disk to other system).
Also it cannot detect if your current kernel have any patches applied or not.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-27 6:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 22:15 recovery of crashed reiserfs disk? Francois-Rene Rideau
2003-01-18 7:09 ` Ookhoi
2003-01-18 8:51 ` Oleg Drokin
2003-01-18 9:01 ` Ookhoi
2003-01-18 11:57 ` Francois-Rene Rideau
2003-01-20 14:20 ` Francois-Rene Rideau
2003-01-21 21:33 ` Crash again! Francois-Rene Rideau
2003-01-22 5:57 ` Ookhoi
2003-01-22 10:03 ` Francois-Rene Rideau
2003-01-24 22:28 ` Crash: the problem was DMA! Francois-Rene Rideau
2003-01-25 16:15 ` Manuel Krause
2003-01-26 18:18 ` mkreiserfs -s 1024 makes unmountable partitions Francois-Rene Rideau
2003-01-27 4:49 ` Ookhoi
2003-01-27 5:23 ` Brian Tinsley
2003-01-27 6:59 ` Oleg Drokin [this message]
2003-01-27 7:20 ` Scott R. Every
2003-01-27 7:25 ` Oleg Drokin
2003-01-27 7:37 ` Scott R. Every
2003-01-27 7:42 ` Oleg Drokin
2003-01-29 11:37 ` Hans Reiser
2003-01-27 11:26 ` Francois-Rene Rideau
2003-01-27 11:33 ` Oleg Drokin
2003-01-27 11:42 ` Francois-Rene Rideau
2003-01-27 12:46 ` Francois-Rene Rideau
2003-01-27 14:20 ` Manuel Krause
2003-01-28 2:41 ` Oh no! Not again! Francois-Rene Rideau
2003-01-28 11:00 ` Vitaly Fertman
2003-01-29 19:31 ` Francois-Rene Rideau
2003-01-29 20:17 ` Vitaly Fertman
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=20030127095957.A22720@namesys.com \
--to=green@namesys.com \
--cc=fare@tunes.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.