Check for ccreg40

Check for ccreg40

[Mat]

Hi,

sure,

debugfs.reiser4 -p /dev/foo

should print everything needed

Regards

Mat

Re: Check for ccreg40

[Edward Shishkin]

Mat wrote:

>Hi,
>
>sure,
>
>debugfs.reiser4 -p /dev/foo
>  
>

No, with the option "-p" debugfs.reiser4 (and other utilities
of reiser4progs package) prints the "default vector of plugins"
and doesn't look at /dev/foo..

Edward.

>should print everything needed
>
>Regards
>
>Mat
>
>--
>To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>

Re: Check for ccreg40

[John]

On Tue, 13 May 2008 03:16:37 +0400, Edward Shishkin <edward.shishkin@gmail.com> wrote:
> Mat wrote:
> 
>>Hi,
>>
>>sure,
>>
>>debugfs.reiser4 -p /dev/foo
>>
>>
> 
> No, with the option "-p" debugfs.reiser4 (and other utilities
> of reiser4progs package) prints the "default vector of plugins"
> and doesn't look at /dev/foo..
> 
> Edward.
> 


Oops I did not see the -t in your email. Correct it showed me what I wanted to know, reg40 :(

Thanks

Re: Check for ccreg40

[Matthew]

On Tue, May 13, 2008 at 1:16 AM, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> Mat wrote:
>
>
> > Hi,
> >
> > sure,
> >
> > debugfs.reiser4 -p /dev/foo
> >
> >
>
>  No, with the option "-p" debugfs.reiser4 (and other utilities
>  of reiser4progs package) prints the "default vector of plugins"
>  and doesn't look at /dev/foo..
>
>  Edward.
>
>
> > should print everything needed
> >
> > Regards
> >
> > Mat
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe reiserfs-devel"
> in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> >
> >
>
>

oops, sorry,
I thought it would print the plugins of the current partition

is there a way by showing the plugins in using grep (e.g. whether it's
used lzo or gzip compression) ?

for example grep 'ccreg shows' the following, that should mean ccreg40
/ cryptcompression was used, correct ?

debugfs.reiser4  -t -f /dev/sdd8 | grep ccreg
debugfs.reiser4 1.0.6
Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
reiser4progs/COPYING.

            create : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)
            object : id = 4 (ccreg40)

Thanks

Mat

Re: Check for ccreg40

[Edward Shishkin]

Matthew wrote:

>On Tue, May 13, 2008 at 1:16 AM, Edward Shishkin
><edward.shishkin@gmail.com> wrote:
>  
>
>  
>
[...]

>is there a way by showing the plugins in using grep (e.g. whether it's
>used lzo or gzip compression) ?
>  
>

grep for "lzo1" or "gzip1".
At least stat-data of root directory must contain it.

>for example grep 'ccreg shows' the following, that should mean ccreg40
>/ cryptcompression was used, correct ?
>
>  
>

yup

>debugfs.reiser4  -t -f /dev/sdd8 | grep ccreg
>debugfs.reiser4 1.0.6
>Copyright (C) 2001-2005 by Hans Reiser, licensing governed by
>reiser4progs/COPYING.
>
>            create : id = 4 (ccreg40)
>            object : id = 4 (ccreg40)
>

Re: Check for ccreg40

[John]

On Mon, 12 May 2008 23:01:50 +0000 (UTC), Mat <jackdachef@gmail.com> wrote:
> Hi,
> 
> sure,
> 
> debugfs.reiser4 -p /dev/foo
> 
> should print everything needed
> 
> Regards
> 
> Mat
>

debugfs.reiser4 1.0.6                                                                               
Copyright (C) 2001-2005 by Hans Reiser, licensing governed by reiser4progs/COPYING.                 
                                                                                                    
Default profile:                                                                                    
create:          "reg40"           (id:0x0 type:0x0)    [Regular file plugin for creat(2)]          
key:             "key_large"       (id:0x1 type:0xb)    [Key plugin]                                
compress:        "lzo1"            (id:0x0 type:0xc)    [Compression plugin]                        
compressMode:    "conv"            (id:0x4 type:0xd)    [Compression Mode plugin]                   
cluster:         "64K"             (id:0x0 type:0x10)   [Cluster plugin]                            
hash:            "r5_hash"         (id:0x1 type:0x3)    [Directory entry hash plugin]               
fibration:       "ext_1_fibre"     (id:0x2 type:0x4)    [Key fibration plugin]                      
formatting:      "smart"           (id:0x2 type:0x5)    [File body formatting plugin]
Error: Device is mounted 'rw' at the moment. Use -f to force over.

I am confused, does reg40 means no compression, or does the compress lzo1 being there means compression?

Thanks

Re: Check for ccreg40

[Maciej Soltysiak]

Hi,

I haven't looked at r4 development for a while now and I have a few 
questions.
> Default profile:                                                                                    
> create:          "reg40"           (id:0x0 type:0x0)    [Regular file plugin for creat(2)]          
> key:             "key_large"       (id:0x1 type:0xb)    [Key plugin]                                
> compress:        "lzo1"            (id:0x0 type:0xc)    [Compression plugin]                        
> compressMode:    "conv"            (id:0x4 type:0xd)    [Compression Mode plugin]                   
> [...]
>
> I am confused, does reg40 means no compression, or does the compress lzo1 being there means compression?
>   
Is it possible to create a regular r4 partition and choose which files 
keep compressed (how?)
or do I have to create a all-compressed partition?

To play with compression can I just use the standard patch from
http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/ 
?

Does this patch include also file-as-directory stuff?

BTW it might be good to change the *Reiser4 is released!* message on

        http://reiser4.erudified.com/install_v4.html

to at least point to

        
http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/

instead of giving a 404.

Best regards,
Maciej

Re: Check for ccreg40

[Edward Shishkin]

Maciej Soltysiak wrote:

> Hi,
>
> I haven't looked at r4 development for a while now and I have a few 
> questions.

[...]

>>
>> I am confused, does reg40 means no compression, or does the compress 
>> lzo1 being there means compression?
>>   
>
> Is it possible to create a regular r4 partition and choose which files 
> keep compressed (how?)


Not yet.
There is a (deprecated) pseudo-file interface, which allows to set
compression et al per directory (the latest patch is against 2.6.13).

> or do I have to create a all-compressed partition?


Yes.
Reiser4 has means to automatically reduce cpu and memory usage on
incompressible data.

With the default plugin scheduler (compressMode: "conv") conversion
will be performed in 2 interfaces:
1. FILE: convert cryptcompress to unix-file plugin;
2. COMPRESS: turn on/off compression in flush time.

However, this scheduler uses very simple heuristics which work
incorrectly on various media files, etc.. I believe it can be improved
to process 80-90% of _all_ files properly.

>
> To play with compression can I just use the standard patch from
> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/ 
> ?
>

Yes.

> Does this patch include also file-as-directory stuff?


No, this stuff was removed (see my comment about pseudo-file interface 
above)

>
> BTW it might be good to change the *Reiser4 is released!* message on
>
>        http://reiser4.erudified.com/install_v4.html
>
> to at least point to
>
>        
> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/ 
>
>
> instead of giving a 404.


This is a temporal place for Hans's whitepaper.
I don't have a time to fix all the links to work properly.

Thanks,
Edward.

Re: Check for ccreg40

[Edward Shishkin]

John wrote:
 >debugfs.reiser4 1.0.6
 >Copyright (C) 2001-2005 by Hans Reiser, licensing governed by 
reiser4progs/COPYING.
 >
 >Default profile:
 >create:          "reg40"           (id:0x0 type:0x0)    [Regular file 
plugin for creat(2)]
 >key:             "key_large"       (id:0x1 type:0xb)    [Key plugin]
 >compress:        "lzo1"            (id:0x0 type:0xc)    [Compression 
plugin]
 >compressMode:    "conv"            (id:0x4 type:0xd)    [Compression 
Mode plugin]
 >cluster:         "64K"             (id:0x0 type:0x10)   [Cluster plugin]
 >hash:            "r5_hash"         (id:0x1 type:0x3)    [Directory 
entry hash plugin]
 >fibration:       "ext_1_fibre"     (id:0x2 type:0x4)    [Key fibration 
plugin]
 >formatting:      "smart"           (id:0x2 type:0x5)    [File body 
formatting plugin]
 >Error: Device is mounted 'rw' at the moment. Use -f to force over.
 >
 >I am confused, does reg40 means no compression, or does the compress 
lzo1 being there means compression?

The first statement is correct.

The above is initial vector of plugins that will be installed by
mkfs.reiser4 to the root directory when formatting a partition
(and then propagated through the semantic tree by the system).
So, actually the option "-p" makes sense only for mkfs utility,
I don't know why other utilities (debugfs, fsck) also show this:
IMHO not a very good idea.

This option is to show resulted vector of plugins _before_ formatting
a partition. Sometimes it is convenient to see what you'll actually
have (especially if you want to override some default values). For
example, "mkfs.reiser4 -p -o create=ccreg40,compress=gzip1" will show:

create:          "ccreg40"         (id:0x4 type:0x0)    [Regular file 
plugin for creat(2)]
key:             "key_large"       (id:0x1 type:0xb)    [Key plugin]
compress:        "gzip1"           (id:0x1 type:0xc)    [Compression plugin]
compressMode:    "conv"            (id:0x4 type:0xd)    [Compression 
Mode plugin]
cluster:         "64K"             (id:0x0 type:0x10)   [Cluster plugin]
hash:            "r5_hash"         (id:0x1 type:0x3)    [Directory entry 
hash plugin]
fibration:       "ext_1_fibre"     (id:0x2 type:0x4)    [Key fibration 
plugin]
formatting:      "smart"           (id:0x2 type:0x5)    [File body 
formatting plugin]

Note, that "compress", "compressMode" and cluster" settings make
sense only with "ccreg40" installed.
Also "formatting" makes sense only with "reg40" installed.
Such dependencies are not well documented, so please keep them in
mind for now..

Edward.

Check for ccreg40

[John]

Hello,

is there a way to check if I enable ccreg40 when I created my partition?
I do not remember anymore what I did with the big partition, and hope I did it but...

So
1- Is there a way to check that?
2- If I forgot is there a way to fix that without mkfs and therefore needing to copy my data elsewhere?


Thanks,

John

Re: Check for ccreg40

[Edward Shishkin]

John wrote:

>Hello,
>
>is there a way to check if I enable ccreg40 when I created my partition?
>  
>

debugfs.reiser4 -t /dev/xxx | grep reg40

The first found string will show if it was formated by reg40 (default) 
or ccreg40 option.

>I do not remember anymore what I did with the big partition, and hope I did it but...
>
>So
>1- Is there a way to check that?
>  
>

So yes, it is (the ugly one for now..)

>2- If I forgot is there a way to fix that without mkfs and therefore needing to copy my data elsewhere?
>  
>

What do you want to fix?

Thanks,
Edward.

Re: Check for ccreg40

[John]

On Tue, 13 May 2008 03:05:43 +0400, Edward Shishkin <edward.shishkin@gmail.com> wrote:
> John wrote:
> 
>>Hello,
>>
>>is there a way to check if I enable ccreg40 when I created my partition?
>>
>>
> 
> debugfs.reiser4 -t /dev/xxx | grep reg40
> 
> The first found string will show if it was formated by reg40 (default)
> or ccreg40 option.
>>
> 
> So yes, it is (the ugly one for now..)
> 
>>
> 
> What do you want to fix?
> 
> Thanks,
> Edward.
> --

1- I did some tests on an empty partition and it is the same output in ccreg40 and reg40 so it is not working here.

2- I want a ccreg40 partition of course, but this is my biggest partition so if it is not I am in trouble to copy files somewhere else...

Thanks