From: Hans Reiser <reiser@namesys.com>
To: Jeff Mahoney <jeffm@suse.com>, vitaly@thebsh.namesys.com
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: [PATCH] reiserfsprogs: Warn on block sizes > 4k
Date: Wed, 29 Jun 2005 15:40:49 -0700 [thread overview]
Message-ID: <42C32371.5080307@namesys.com> (raw)
In-Reply-To: <42B9AAAB.2030208@suse.com>
Vitaly, please reply. Thanks much Jeff, we needed this.
Hans
Jeff Mahoney wrote:
>
> Hello all -
>
> Filesystems created with block size > page size will not work until that
> support is added to the kernel. Filesystems with block size > 4k (lowest
> page size supported in Linux) will not work on all systems. This patch
> adds a check and a warning in those conditions, informing the user of
> the caveats of using a larger block size. It can be overridden with -f.
>
> Patch attached, please apply.
>
> -Jeff
>
> --
> Jeff Mahoney
> SuSE Labs
-------------------------
Subject: [PATCH] reiserfsprogs: Warn on block sizes > 4k
From: Jeff Mahoney <jeffm@suse.com>
Filesystems created with block size > page size will not work until that
support is added to the kernel. Filesystems with block size > 4k (lowest
page size supported in Linux) will not work on all systems. This patch
adds a check and a warning in those conditions, informing the user of the
caveats of using a larger block size. It can be overridden with -f.
diff -ruNp reiserfsprogs-3.6.19/mkreiserfs/mkreiserfs.c
reiserfsprogs-3.6.19.devel/mkreiserfs/mkreiserfs.c
--- reiserfsprogs-3.6.19/mkreiserfs/mkreiserfs.c 2004-09-30
23:04:21.000000000 +0200
+++ reiserfsprogs-3.6.19.devel/mkreiserfs/mkreiserfs.c 2005-06-22
19:26:58.221711866 +0200
@@ -684,6 +684,9 @@ int main (int argc, char **argv)
if (!(mode & QUIET_MODE) && !can_we_format_it (device_name, force))
return 1;
+
+ if (!(mode & QUIET_MODE) && !block_size_ok (Block_size, force))
+ return 1;
if (jdevice_name)
if (!(mode & QUIET_MODE) && !can_we_format_it (jdevice_name,
force))
diff -ruNp reiserfsprogs-3.6.19/reiserfscore/reiserfslib.c
reiserfsprogs-3.6.19.devel/reiserfscore/reiserfslib.c
--- reiserfsprogs-3.6.19/reiserfscore/reiserfslib.c 2004-10-04
22:39:35.000000000 +0200
+++ reiserfsprogs-3.6.19.devel/reiserfscore/reiserfslib.c 2005-06-22
20:07:38.015345826 +0200
@@ -1175,6 +1175,24 @@ void make_sure_root_dir_exists (reiserfs
&parent_root_dir_key, ih_flags);
}
+int block_size_ok (int blocksize, int force)
+{
+ int pagesize = getpagesize();
+ if (blocksize > 4096) {
+ reiserfs_warning (stderr, "Block sizes larger than 4k are not "
+ "supported on all architectures.\n");
+ if (blocksize > pagesize)
+ reiserfs_warning (stderr, "The newly created filesystem
will not "
+ "be mountable on this system.\n");
+ else
+ reiserfs_warning (stderr, "The newly created filesystem may
not "
+ "be mountable on other systems.\n");
+ check_forcing_ask_confirmation (force);
+ }
+
+ return 1;
+}
+
/* we only can use a file for filesystem or journal if it is either not
mounted block device or regular file and we are forced to use it */
prev parent reply other threads:[~2005-06-29 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 18:15 [PATCH] reiserfsprogs: Warn on block sizes > 4k Jeff Mahoney
2005-06-29 22:40 ` Hans Reiser [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=42C32371.5080307@namesys.com \
--to=reiser@namesys.com \
--cc=jeffm@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@thebsh.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.