Apache2 problems

Apache2 problems

[Tom Lanyon]

Hello,

Can someone please inform me of how to stop the dreaded sendfile
issues while using reiser4 and apache2?

I just setup reiser4 on a nice new hard drive and tried to run apache2
and ended up with many kernel panics and then the machine locked up.

I thought this issue was fixed in reiser4? If not, how can I go about
stopping this from happening?

This is reiser4-2004.07.23-19.37-linux-2.6.8-rc2-bk4.diff  on a
2.6.8-rc2 kernel.
I'm about to try the latest snapshot on a vanilla 2.6.8-rc3 and see if
it helps..


Thanks for any help,

Tom.

Re: Apache2 problems

[mjt]

On Tue, Aug 10, 2004 at 02:55:55AM +0930, Tom Lanyon wrote:
>
>This is reiser4-2004.07.23-19.37-linux-2.6.8-rc2-bk4.diff  on a
>2.6.8-rc2 kernel.

I would suggest using such an old snapshot.

According to Namesys (Zam iirc) the bug has been fixed.

>I'm about to try the latest snapshot on a vanilla 2.6.8-rc3 and see if
>it helps..

Please do.

-- 
mjt

Re: Apache2 problems

[Hans Reiser]

Markus Törnqvist wrote:

>On Tue, Aug 10, 2004 at 02:55:55AM +0930, Tom Lanyon wrote:
>  
>
>>This is reiser4-2004.07.23-19.37-linux-2.6.8-rc2-bk4.diff  on a
>>2.6.8-rc2 kernel.
>>    
>>
>
>I would suggest
>
forgot the not ;-), but I at least understood you.

> using such an old snapshot.
>
>According to Namesys (Zam iirc) the bug has been fixed.
>
>  
>
>>I'm about to try the latest snapshot on a vanilla 2.6.8-rc3 and see if
>>it helps..
>>    
>>
>
>Please do.
>
>  
>

Re: Apache2 problems

[Tom Lanyon]

Hehe yeah I understood too... i'm compiling new kernel with newer
reiser4 now to see if it helps..

On Mon, 09 Aug 2004 10:50:00 -0700, Hans Reiser <reiser@namesys.com> wrote:
> Markus Törnqvist wrote:
> 
> >On Tue, Aug 10, 2004 at 02:55:55AM +0930, Tom Lanyon wrote:
> >
> >
> >>This is reiser4-2004.07.23-19.37-linux-2.6.8-rc2-bk4.diff  on a
> >>2.6.8-rc2 kernel.
> >>
> >>
> >
> >I would suggest
> >
> forgot the not ;-), but I at least understood you.
> 
> 
> 
> > using such an old snapshot.
> >
> >According to Namesys (Zam iirc) the bug has been fixed.
> >
> >
> >
> >>I'm about to try the latest snapshot on a vanilla 2.6.8-rc3 and see if
> >>it helps..
> >>
> >>
> >
> >Please do.
> >
> >
> >
> 
>

Re: Apache2 problems

[Alex Zarochentsev]

On Tue, Aug 10, 2004 at 02:55:55AM +0930, Tom Lanyon wrote:
> Hello,
> 
> Can someone please inform me of how to stop the dreaded sendfile
> issues while using reiser4 and apache2?
> 
> I just setup reiser4 on a nice new hard drive and tried to run apache2
> and ended up with many kernel panics and then the machine locked up.
> 
> I thought this issue was fixed in reiser4? If not, how can I go about
> stopping this from happening?

> This is reiser4-2004.07.23-19.37-linux-2.6.8-rc2-bk4.diff  on a
> 2.6.8-rc2 kernel.

it seems to me there is no reiser4-2004.07.23-19.37-linux-2.6.8-rc2-bk4.diff on
the namesys web site.

> I'm about to try the latest snapshot on a vanilla 2.6.8-rc3 and see if
> it helps..

the snapshot is for linux-2.6.8-rc2-mm2, not -rc2.
latest auto-snapshots is for linux-2.6.8-rc3-mm1

> Thanks for any help,
> Tom.

-- 
Alex.

Re: Apache2 problems

[Alex Zarochentsev]

On Tue, Aug 10, 2004 at 02:55:55AM +0930, Tom Lanyon wrote:
> Hello,
> 
> Can someone please inform me of how to stop the dreaded sendfile
> issues while using reiser4 and apache2?
> 
> I just setup reiser4 on a nice new hard drive and tried to run apache2
> and ended up with many kernel panics and then the machine locked up.

I used ab2 test tool, apache2 from SuSE9.1 and the latest reiser4 code.
It works fine for me.

> 
> I thought this issue was fixed in reiser4? If not, how can I go about
> stopping this from happening?
> 
> This is reiser4-2004.07.23-19.37-linux-2.6.8-rc2-bk4.diff  on a
> 2.6.8-rc2 kernel.
> I'm about to try the latest snapshot on a vanilla 2.6.8-rc3 and see if
> it helps..
> 
> 
> Thanks for any help,
> 
> Tom.

-- 
Alex.

fsck.reiser4 wrong size error (?)

[Francesco Biscani]

Hi,

lately whenever I run fsck.reiser4 I get loads of errors about wrong sizes, 
e.g., something like [1] "Object foo (stat40) has wrong size, should be X 
bytes". fsck suggests to --fix them, which I do, and indeed another run of 
fsck confirms that there are no problems. However after mounting the 
partition and working a bit on it, I get those size errors again, even if the 
partition was umounted cleanly. This happens:

- with 0.5.6, 0.5.6-fixed and 1.0.0 reiser4progs,
- on two different partitions on two different machines,
- before and after updating the fs layout (by means of debugfs -C).

I'm running the latest _stable_ snapshot (against 2.6.8-rc2-mm2), but I 
remember this happening also with previous auto-snapshot (though it did not 
use to happen in my early 0.5.6 days). What's going on here?

Regards,

  Francesco



[1] Sorry, I don't remember exactly the error message, will post it if needed.

Re: fsck.reiser4 wrong size error (?)

[Vitaly Fertman]

On Tuesday 10 August 2004 21:48, Francesco Biscani wrote:
> Hi,
>
> lately whenever I run fsck.reiser4 I get loads of errors about wrong sizes,
> e.g., something like [1] "Object foo (stat40) has wrong size, should be X
> bytes". fsck suggests to --fix them, which I do, and indeed another run of
> fsck confirms that there are no problems. However after mounting the
> partition and working a bit on it, I get those size errors again, even if
> the partition was umounted cleanly. This happens:
>
> - with 0.5.6, 0.5.6-fixed and 1.0.0 reiser4progs,
> - on two different partitions on two different machines,
> - before and after updating the fs layout (by means of debugfs -C).
>
> I'm running the latest _stable_ snapshot (against 2.6.8-rc2-mm2), but I
> remember this happening also with previous auto-snapshot (though it did not
> use to happen in my early 0.5.6 days). What's going on here?
>
> Regards,
>
>   Francesco
>
>
>
> [1] Sorry, I don't remember exactly the error message, will post it if
> needed.

are messages about 'wrong size' or about 'wrong bytes' or both?

-- 
Thanks,
Vitaly Fertman

Re: fsck.reiser4 wrong size error (?)

[Francesco Biscani]

Hi,

> are messages about 'wrong size' or about 'wrong bytes' or both?

I'm _almost_ sure it's about "wrong bytes". I'll confirm ASAP. Are they 
potentially harmful?

Oh, BTW, "debugfs -C" worked ok here.

Regards,

  Francesco

Re: fsck.reiser4 wrong size error (?)

[Vitaly Fertman]

On Tuesday 10 August 2004 22:09, Francesco Biscani wrote:
> Hi,
>
> > are messages about 'wrong size' or about 'wrong bytes' or both?
>
> I'm _almost_ sure it's about "wrong bytes". I'll confirm ASAP. Are they
> potentially harmful?

no, they are not harmful. but anyway need to be fixed.

> Oh, BTW, "debugfs -C" worked ok here.

great.

-- 
Thanks,
Vitaly Fertman

Re: fsck.reiser4 wrong size error (?)

[Vladimir V. Saveliev]

Hello

Francesco Biscani wrote:
> Hi,
> 
> 
>>are messages about 'wrong size' or about 'wrong bytes' or both?
> 
> 
> I'm _almost_ sure it's about "wrong bytes". I'll confirm ASAP. Are they 
> potentially harmful?
>

wrong bytes is harmless. There was a bug recently which counted each byte twice. It is fixed already.
fsck --fix will fix this kind of corruptions.


> Oh, BTW, "debugfs -C" worked ok here.
> 
> Regards,
> 
>   Francesco
> 
> 

Re: fsck.reiser4 wrong size error (?)

[Francesco Biscani]

On Tuesday 10 August 2004 20:09, Francesco Biscani wrote:
> Hi,
>
> > are messages about 'wrong size' or about 'wrong bytes' or both?
>
> I'm _almost_ sure it's about "wrong bytes". I'll confirm ASAP. Are they
> potentially harmful?
>
> Oh, BTW, "debugfs -C" worked ok here.
>
> Regards,
>
>   Francesco

An update for those interested:

- it was a "wrong bytes" message. All the bytes of affected objects were 
doubled. Corrected with --fix and using now auto-snapshot for 2.6.8-rc4-mm1. 
Let's see if it happens again.
- debugfs -C worked ok also on my / partition.

BTW, debugfs -p showed also that the default plugin for fibration was changed, 
from dot-o to ext-1. But if I create a dir it is still dot-o-fibrated. Am I 
missing something here? Should I mount with some special options to have 
ext-1 fibration as default?

Thanks,

  Francesco

Re: fsck.reiser4 wrong size error (?)

[Alex Zarochentsev]

On Thu, Aug 12, 2004 at 09:38:46PM +0200, Francesco Biscani wrote:
> On Tuesday 10 August 2004 20:09, Francesco Biscani wrote:
> > Hi,
> >
> > > are messages about 'wrong size' or about 'wrong bytes' or both?
> >
> > I'm _almost_ sure it's about "wrong bytes". I'll confirm ASAP. Are they
> > potentially harmful?
> >
> > Oh, BTW, "debugfs -C" worked ok here.
> >
> > Regards,
> >
> >   Francesco
> 
> An update for those interested:
> 
> - it was a "wrong bytes" message. All the bytes of affected objects were 
> doubled. Corrected with --fix and using now auto-snapshot for 2.6.8-rc4-mm1. 
> Let's see if it happens again.
> - debugfs -C worked ok also on my / partition.
> 
> BTW, debugfs -p showed also that the default plugin for fibration was changed, 
> from dot-o to ext-1. But if I create a dir it is still dot-o-fibrated. Am I 
> missing something here? Should I mount with some special options to have 
> ext-1 fibration as default?

a. mkfs.reiser4 has options to set default fibration plugin.
b. you can change fibration plugin for empty dir through metas/ interface.

darkstar:/mnt/testfs # mkdir foo
darkstar:/mnt/testfs # cat foo/metas/plugin/fibration ; echo
2 ext-1 fibrate file by single character extension
darkstar:/mnt/testfs # echo -e "dot-o\0" > foo/metas/plugin/fibration
darkstar:/mnt/testfs # cat foo/metas/plugin/fibration ; echo
1 dot-o fibrate .o files separately

darkstar:/mnt/testfs # mkdir foo/bar
darkstar:/mnt/testfs # cat foo/bar/metas/plugin/fibration
1 dot-o fibrate .o files separately

> Thanks,
> 
>   Francesco

-- 
Alex.

Re: fsck.reiser4 wrong size error (?)

[Vitaly Fertman]

On Thursday 12 August 2004 23:38, Francesco Biscani wrote:
> On Tuesday 10 August 2004 20:09, Francesco Biscani wrote:
> > Hi,
> >
> > > are messages about 'wrong size' or about 'wrong bytes' or both?
> >
> > I'm _almost_ sure it's about "wrong bytes". I'll confirm ASAP. Are they
> > potentially harmful?
> >
> > Oh, BTW, "debugfs -C" worked ok here.
> >
> > Regards,
> >
> >   Francesco
>
> An update for those interested:
>
> - it was a "wrong bytes" message. All the bytes of affected objects were
> doubled. Corrected with --fix and using now auto-snapshot for
> 2.6.8-rc4-mm1. Let's see if it happens again.

this was fixed recently.

> - debugfs -C worked ok also on my / partition.
>
> BTW, debugfs -p showed also that the default plugin for fibration was
> changed, from dot-o to ext-1. But if I create a dir it is still
> dot-o-fibrated. Am I missing something here? Should I mount with some
> special options to have ext-1 fibration as default?

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,
Vitaly Fertman

Re: fsck.reiser4 wrong size error (?)

[Francesco Biscani]

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?
2) is there a place where a detailed description of mount options for reiser4 
is available? I've googled around without much luck.

Thanks again,

  Francesco

Re: fsck.reiser4 wrong size error (?)

[Alex Zarochentsev]

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.

Re: fsck.reiser4 wrong size error (?)

[mjt]

On Fri, Aug 13, 2004 at 01:16:12PM +0400, Alex Zarochentsev wrote:

>So, the problen cannot be fully solved.  However, you can re-create all second
>level sub-directories and assign another fibration plugins to them.

I've never gotten a real reply this question...
Will it be possible in the future to refibrate, and otherwise change
the already-set plugin settings for directories?

Are you thinking about implementing it/is it a matter of time and money?

Thanks!

-- 
mjt

Re: fsck.reiser4 wrong size error (?)

[Vladimir V. Saveliev]

Hello

Markus Törnqvist wrote:
> On Fri, Aug 13, 2004 at 01:16:12PM +0400, Alex Zarochentsev wrote:
> 
> 
>>So, the problen cannot be fully solved.  However, you can re-create all second
>>level sub-directories and assign another fibration plugins to them.
> 
> 
> I've never gotten a real reply this question...
> Will it be possible in the future to refibrate, and otherwise change
> the already-set plugin settings for directories?
> 

I think only empty directory can be refibrated.

> Are you thinking about implementing it/is it a matter of time and money?
> 

Reiser4 provides plugin mechanism. Everyone is encouraged to write plugins.

> Thanks!
> 

Re: fsck.reiser4 wrong size error (?)

[mjt]

On Fri, Aug 13, 2004 at 01:43:33PM +0400, Vladimir V. Saveliev wrote:
>
>I think only empty directory can be refibrated.
>>Are you thinking about implementing it/is it a matter of time and money?
>Reiser4 provides plugin mechanism. Everyone is encouraged to write plugins.

Aren't those two sentences a bit contradictory?-)

I mean, if it's possible only to (re)fibrate empty directories, is it
impossbile to write a means of refibration to a new plugin or the existing
plugin? :)

Thanks!

-- 
mjt

Re: fsck.reiser4 wrong size error (?)

[Vladimir V. Saveliev]

Hello

Markus Törnqvist wrote:
> On Fri, Aug 13, 2004 at 01:43:33PM +0400, Vladimir V. Saveliev wrote:
> 
>>I think only empty directory can be refibrated.
>>
>>>Are you thinking about implementing it/is it a matter of time and money?
>>
>>Reiser4 provides plugin mechanism. Everyone is encouraged to write plugins.
> 
> 
> Aren't those two sentences a bit contradictory?-)
> 
> I mean, if it's possible only to (re)fibrate empty directories, is it
> impossbile to write a means of refibration to a new plugin or the existing
> plugin? :)
> 
well, second sentence is not about this certain plugin

as for refibrating a directory - it probably can be done by simple shell script

> Thanks!
> 

Re: fsck.reiser4 wrong size error (?)

[Nikita Danilov]

Markus Törnqvist writes:
 > On Fri, Aug 13, 2004 at 01:43:33PM +0400, Vladimir V. Saveliev wrote:
 > >
 > >I think only empty directory can be refibrated.
 > >>Are you thinking about implementing it/is it a matter of time and money?
 > >Reiser4 provides plugin mechanism. Everyone is encouraged to write plugins.
 > 
 > Aren't those two sentences a bit contradictory?-)
 > 
 > I mean, if it's possible only to (re)fibrate empty directories, is it
 > impossbile to write a means of refibration to a new plugin or the existing
 > plugin? :)

Currently echo 'foo' > foo/metas/plugin/fibration

simply changes id of fibration plugin associated with foo. Doing this
on non-empty foo would result in corruption and hence is
disabled. Vladimir, as far as I can tell, meant that if one writes
support for re-fibrating directory content, changing fibration plugin
on non-empty directory can be allowed.

If I were going to implement such thing, I would proceed as follows:

 - mark directory stat-data (on-disk) in special way. Any normal
 access to marked directory returns EBUSY.

 - start re-fibrating directory content.

 - use safe-link mechanism to assure that if crash happens during
 re-fibration, it will be continued on next mount. (Yes, this sounds
 like possible DoS for a large directory, so probably only `user with
 proper permissions' should be allowed to do re-fibration.)

 - when re-fibration is completed, clear mark from stat-data.

 > 
 > Thanks!
 > 
 > -- 
 > mjt
 > 

Nikita.

 > 

Re: fsck.reiser4 wrong size error (?)

[mjt]

On Fri, Aug 13, 2004 at 02:00:04PM +0400, Nikita Danilov wrote:
>
>simply changes id of fibration plugin associated with foo. Doing this
>on non-empty foo would result in corruption and hence is
>disabled. Vladimir, as far as I can tell, meant that if one writes

And on a file it would do nothing, I assume, ever.

>If I were going to implement such thing, I would proceed as follows:

Hooray!

Thanks for the pointers, maybe that's what I should try some time when
I have too much time :)

But you may remember what happened when I last tried to touch Reiser4
code and VFS ;)

-- 
mjt

Re: fsck.reiser4 wrong size error (?)

[Vladimir V. Saveliev]

Hello

Markus Törnqvist wrote:
> On Fri, Aug 13, 2004 at 02:00:04PM +0400, Nikita Danilov wrote:
> 
>>simply changes id of fibration plugin associated with foo. Doing this
>>on non-empty foo would result in corruption and hence is
>>disabled. Vladimir, as far as I can tell, meant that if one writes
> 
> 
> And on a file it would do nothing, I assume, ever.
> 
> 
>>If I were going to implement such thing, I would proceed as follows:
> 
> 
> Hooray!
> 
> Thanks for the pointers, maybe that's what I should try some time when
> I have too much time :)
> 
> But you may remember what happened when I last tried to touch Reiser4
> code and VFS ;)
> 

Sorry, i do not. What was it?

Re: fsck.reiser4 wrong size error (?)

[mjt]

On Fri, Aug 13, 2004 at 02:46:03PM +0400, Vladimir V. Saveliev wrote:
>>But you may remember what happened when I last tried to touch Reiser4
>>code and VFS ;)
>Sorry, i do not. What was it?

Nikita gave me the theory on how to access metas/ on read-only files
by hacking a new attribute into VFS.

Unfortunately it first rendered all files inaccessible by anyone but
root and when I tried to add debug code the kernel would panic at boot.

Then I didn't have time to pursue the matter.
Besides, I don't think all filesystem maintainers would like that feature.

-- 
mjt

Re: fsck.reiser4 wrong size error (?)

[Francesco Biscani]

Hi,

On Friday 13 August 2004 11:16, Alex Zarochentsev wrote:
> 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.

Would something like this be appropriate:

# mkdir /bin_new
# echo -e "ext-1\0" > /bin_new/metas/plugin/fibration
# cp -a /bin/* /bin_new/
# rm -fr /bin
# mv /bin_new /bin

Could this break systems or applications that relies on mtimes or other 
file/dir attributes? (Gentoo's portage system comes to mind) The "-a" option 
of cp should make this safe IMO.

> fs/reiser4/vfs_opts.c:reiser4_parse_options contains opts[] -- an array of
> all reiser4 mount option descriptions.

I'll look into that. Thanks for the pointer.

Thanks very much for the reply,

  Francesco

Re: fsck.reiser4 wrong size error (?)

[Matt Stegman]

On Fri, 13 Aug 2004, Francesco Biscani wrote:

> Hi,
>
> On Friday 13 August 2004 11:16, Alex Zarochentsev wrote:
> > 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.
>
> Would something like this be appropriate:
>
> # mkdir /bin_new
> # echo -e "ext-1\0" > /bin_new/metas/plugin/fibration
> # cp -a /bin/* /bin_new/
> # rm -fr /bin
> # mv /bin_new /bin
>
> Could this break systems or applications that relies on mtimes or other
> file/dir attributes? (Gentoo's portage system comes to mind) The "-a" option
> of cp should make this safe IMO.

The ctime will be updated.  'cp -a' cannot preserve the ctime field.
Whether or not your application uses the ctime is something you'll have to
determine (backup software usually does, for example).

cp also does not copy EAs or ACLs, or any attributes set by chattr (not
applicable to reiser4).  Any other attributes or permissions unique to
reiser4 would also not be copied.

-- 
Matt Stegman

Re: fsck.reiser4 wrong size error (?)

[Francesco Biscani]

Hi,

On Friday 13 August 2004 22:26, Matt Stegman wrote:
> The ctime will be updated.  'cp -a' cannot preserve the ctime field.
> Whether or not your application uses the ctime is something you'll have to
> determine (backup software usually does, for example).

I was thinking of gentoo's package system, which uses mtimes to detect if a 
file belonging to a certain package has been modified or overwritten. This 
way when uninstalling the package, that particular file is not removed 
because his mtime differs from the one present in the packages database.

cp man page says that the -p switch, implied by -a, preserves "the original 
files' owner, group, permissions, and timestamps." So the question is: is 
mtime included in "timestamps"?

> cp also does not copy EAs or ACLs, or any attributes set by chattr (not
> applicable to reiser4).  Any other attributes or permissions unique to
> reiser4 would also not be copied.

This would not certainly be a problem.

Thanks very much,

  Francesco

Re: fsck.reiser4 wrong size error (?)

[Matt Stegman]

On Fri, 13 Aug 2004, Francesco Biscani wrote:
> cp man page says that the -p switch, implied by -a, preserves "the original
> files' owner, group, permissions, and timestamps." So the question is: is
> mtime included in "timestamps"?

Yes, mtime and atime are reset on the destination file after the copy.

-- 
Matt Stegman

Re: fsck.reiser4 wrong size error (?)

[mjt]

On Fri, Aug 13, 2004 at 03:26:26PM -0500, Matt Stegman wrote:
>
>cp also does not copy EAs or ACLs, or any attributes set by chattr (not
>applicable to reiser4).  Any other attributes or permissions unique to
>reiser4 would also not be copied.

Until cp gets patched to support these ;)

-- 
mjt