From: Edward Shishkin <edward.shishkin@gmail.com>
To: reiserfs-devel <reiserfs-devel@vger.kernel.org>, dimas000@ya.ru
Subject: Re: reiser4 kernel compilation problem.
Date: Mon, 25 Nov 2013 20:37:44 +0100 [thread overview]
Message-ID: <5293A708.2090907@gmail.com> (raw)
In-Reply-To: <20131125190313.79962097@Ulf.tvoe.tv>
On 11/25/2013 04:03 PM, dimas wrote:
>> Fsck doesn't report if compression has been enabled.
>> debugfs.reiser4 should be patched to show value of "create" (reg40 or
>> ccreg40),
>> "compress" (lzo1, or gzip1), etc.
> oh, didn't know, thanks! i thought that "format40" is just equal to "reg40".
Not really.
"format4x" is per-volume thing, whereas "reg4x" is per-directory thing.
BTW, "ccreg40" is bad name: I insisted on "reg41", but reiser4progs
authors were too lazy to change things...
> thus, there is currently no way to determine fs format (reg40 or ccreg40)
Volume format (only "format40" for now) is determined at mkfs time.
"Create" value (only reg40 and ccreg40 for now) of root directory is
determined at mkfs time and inherited by children.
You can change "create" value of any directory (including the root one)
at any time (e.g. with ioctl(2) ), so that new children will inherit
that new value (not implemented).
> and
> compression type (if any)? maybe, such information in fsck would be nice?))
Actually, fsck is to check consistency.#0 SD (stat40):
[29:1(SD):0:2a:0] OFF=28, LEN=94, flags=0x0
exts: 3
mask: 0x13
plugin: sdext_lw
offset: 2
len: 14
mode: drwxr-xr-x
nlink: 4
size: 3
plugin: sdext_unix
offset: 16
len: 28
uid: 0
gid: 0
atime: Mon Nov 4 21:22:24 2013
mtime: Mon Nov 4 21:13:07 2013
ctime: Mon Nov 4 21:13:07 2013
rdev: 150
bytes: 150
plugin: sdext_plugin_set
offset: 44
len: 50
Pset count: 12
permission : id = 0
formatting : id = 2 (smart)
hash : id = 1 (r5_hash)
fibration : id = 2 (ext_1_fibre)
statdata : id = 0 (stat40)
diritem : id = 2 (cde40)
crypto : id = 0
digest : id = 0
compress : id = 0 (lzo1)
compressMode : id = 4 (conv)
cluster : id = 0 (64K)
create : id = 0 (reg40)
There is a special tool for such needs (debugfs.reiser4).
With the option -t it dumps the whole tree. You should
find any stat-data item, and take a look at the "create"
parameter.
In the following example compression has been disabled:
#0 SD (stat40): [29:1(SD):0:2a:0] OFF=28, LEN=94, flags=0x0
exts: 3
mask: 0x13
plugin: sdext_lw
offset: 2
len: 14
mode: drwxr-xr-x
nlink: 4
size: 3
plugin: sdext_unix
offset: 16
len: 28
uid: 0
gid: 0
atime: Mon Nov 4 21:22:24 2013
mtime: Mon Nov 4 21:13:07 2013
ctime: Mon Nov 4 21:13:07 2013
rdev: 150
bytes: 150
plugin: sdext_plugin_set
offset: 44
len: 50
Pset count: 12
permission : id = 0
formatting : id = 2 (smart)
hash : id = 1 (r5_hash)
fibration : id = 2 (ext_1_fibre)
statdata : id = 0 (stat40)
diritem : id = 2 (cde40)
crypto : id = 0
digest : id = 0
compress : id = 0 (lzo1)
compressMode : id = 4 (conv)
cluster : id = 0 (64K)
create : id = 0 (reg40)
next prev parent reply other threads:[~2013-11-25 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 13:01 reiser4 kernel compilation problem doiggl
2013-11-23 12:13 ` dimas
2013-11-23 8:55 ` doiggl
2013-11-25 9:53 ` Nicolas Barbier
2013-11-25 9:56 ` dimas
2013-11-25 11:30 ` Edward Shishkin
2013-11-25 15:03 ` dimas
2013-11-25 19:37 ` Edward Shishkin [this message]
2013-11-26 14:58 ` doiggl
2013-11-26 21:04 ` dimas
2013-11-28 21:57 ` Edward Shishkin
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=5293A708.2090907@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=dimas000@ya.ru \
--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 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.