From: Alex Zarochentsev <zam@namesys.com>
To: Francesco Biscani <frbiscani@jumpy.it>
Cc: reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 wrong size error (?)
Date: Fri, 13 Aug 2004 13:16:12 +0400 [thread overview]
Message-ID: <20040813091612.GF13834@backtop.namesys.com> (raw)
In-Reply-To: <200408122308.06962.frbiscani@jumpy.it>
On Thu, Aug 12, 2004 at 11:08:06PM +0200, Francesco Biscani wrote:
> Hi,
>
> On Thursday 12 August 2004 22:08, Alex Zarochentsev wrote:
> > a. mkfs.reiser4 has options to set default fibration plugin.
> > b. you can change fibration plugin for empty dir through metas/ interface.
>
> and
>
> On Thursday 12 August 2004 22:31, Vitaly Fertman wrote:
> > default plugins in progs play role for mkfs only, and they have nothing to
> > do with already created fs. You have created it with dot-o default, so the
> > current fibration fs default is dot-o, and you can change it for some
> > partitcular directory only, an empty one, with :
> > echo -e "ext-1\0" > dir/metas/plugin/fibration
> > Then all children will be created with with ext-1 also.
>
> Thanks for the quick response Alex and Vitaly.
>
> I know about the metas interface. What I would like to know, though, is:
>
> 1) is there a way to have all newly created dirs default to ext-1 fibrate,
> without re-creating the fs with mkfs?
Changing fs root dir fibration plugin would do that if the root dir was empty.
Current code does not allow it.
So, the problen cannot be fully solved. However, you can re-create all second
level sub-directories and assign another fibration plugins to them.
> 2) is there a place where a detailed description of mount options for reiser4
> is available? I've googled around without much luck.
fs/reiser4/vfs_opts.c:reiser4_parse_options contains opts[] -- an array of
all reiser4 mount option descriptions.
...
opt_desc_t opts[] = {
/* trace_flags=N
set trace flags to be N for this mount. N can be C numeric
literal recognized by %i scanf specifier. It is treated as
bitfield filled by values of debug.h:reiser4_trace_flags
enum
*/
SB_FIELD_OPT(trace_flags, "%i"),
/* log_flags=N
...
> Thanks again,
> Francesco
--
Alex.
next prev parent reply other threads:[~2004-08-13 9:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 17:25 Apache2 problems Tom Lanyon
2004-08-09 17:29 ` mjt
2004-08-09 17:50 ` Hans Reiser
2004-08-09 17:59 ` Tom Lanyon
2004-08-09 19:59 ` Alex Zarochentsev
2004-08-10 11:31 ` Alex Zarochentsev
2004-08-10 17:48 ` fsck.reiser4 wrong size error (?) Francesco Biscani
2004-08-10 17:56 ` Vitaly Fertman
2004-08-10 18:09 ` Francesco Biscani
2004-08-10 18:30 ` Vitaly Fertman
2004-08-10 18:37 ` Vladimir V. Saveliev
2004-08-12 19:38 ` Francesco Biscani
2004-08-12 20:08 ` Alex Zarochentsev
2004-08-12 20:31 ` Vitaly Fertman
2004-08-12 21:08 ` Francesco Biscani
2004-08-13 9:16 ` Alex Zarochentsev [this message]
2004-08-13 9:31 ` mjt
2004-08-13 9:43 ` Vladimir V. Saveliev
2004-08-13 9:44 ` mjt
2004-08-13 9:50 ` Vladimir V. Saveliev
2004-08-13 10:00 ` Nikita Danilov
2004-08-13 10:01 ` mjt
2004-08-13 10:46 ` Vladimir V. Saveliev
2004-08-13 11:10 ` mjt
2004-08-13 20:06 ` Francesco Biscani
2004-08-13 20:26 ` Matt Stegman
2004-08-13 20:45 ` Francesco Biscani
2004-08-13 20:54 ` Matt Stegman
2004-08-14 8:46 ` mjt
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=20040813091612.GF13834@backtop.namesys.com \
--to=zam@namesys.com \
--cc=frbiscani@jumpy.it \
--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.