reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Reiserfs development mailing list <reiserfs-devel@vger.kernel.org>
Subject: [PATCH 0/2] reiser4: node41 layout support
Date: Tue, 10 Feb 2015 18:58:22 +0100	[thread overview]
Message-ID: <54DA46BE.80302@gmail.com> (raw)

Hi all,

The following patches introduce a new node format(plugin): node41.
The new node layout (node41) contains a 32-bit field. This is the
single difference from the old node format (node40).

The new field will be for meta-data checksums. Currently it is
filled with zeros.

This is an important example of how to add a plugin to reiser4.
Earlier file system developers used to design disk layouts "once
and forever". Any change in disk layouts of such poorly designed
file systems led to compatibility issues and ugly workarounds.
With reiser4 we don't have such problems.

Low-level interface to access the new field

1) in reiser4:

nh41_get_csum(node41_header *head);
nh41_set_csum(node41_header *head, __u32 val);

2) in reiser4progs:

nh41_get_csum(reiser4_node_t *node);
nh41_set_csum(reiser4_node_t *node, uint32_t val);

How to test the new feature:
WARNING: don't use it for important data for now!!!

. format a reiser4 partition with mkfs option "-o node=node41";
. mount as usual;
. use as usual: all previously implemented functionality has to
   work with the new node41 plugin;
. umount;
. debugfs.reiser4 -t /dev/xxx prints a new field CSUM for nodes
   of the new format (0 for now);
. fsck has to check/repair file systems with node41 layouts
   properly.

Please, report if any problems,

Thanks,
Edward.

                 reply	other threads:[~2015-02-10 17:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=54DA46BE.80302@gmail.com \
    --to=edward.shishkin@gmail.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;
as well as URLs for NNTP newsgroup(s).