reiser4 corruption on initial copy

reiser4 corruption on initial copy

[Peter]

I recently copied over my / partition from a reiserfs to a reiser4
partition. This may be user error, but I wanted to report it anyway.

Booting off a live cd- I did the following.

mount source partition -o ro,noatime
mount destination partition -o rw,noatime

# cd source partition
# tar --one-file-system -cvf - | tar -C dest -xf -

Tar went along fine. At the end, there was a very long pause, about a
minute, after the last file (a symlink to /var) was copied. Then the
prompt returned.

On booting up, there were a stream of kernel errors, etc. So I booted
another / and fsck destination partition.

It found one error in a file, just before the last file (/var symlink)
copied. I fixed it, it removed the file (/sbin/uname). Recopied it over
from the source partition. 

After this, the partition works fine.

I wanted to know: 1) did I copy over the stuff wrong? I also used cp -ax
and had the same problems except this time the disk could not be repaired.
2) I did run badblocks on the dest, and it was clean. 3) I am using the
patch from 2.6.17.3 and in my kernel, I have full preempt and cfq
scheduling.

Any feedback appreciated! Thx and keep up the good work.

-- 
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via 
jabber: pete4abw at jabber.org
ICQ: 73676357

Re: reiser4 corruption on initial copy

[Peter]

On Fri, 01 Sep 2006 11:02:58 +0000, Peter wrote:
> 
> # cd source partition
> # tar --one-file-system -cvf - | tar -C dest -xf -
> 
of course I had * for all files :)

I also did the same with rsync -a /mnt/dest. I then thought perhaps the
livecd did not properly unmount the local filesystems, so I issued the
umount command. This took approximately three minutes. I then ran an fsck
and it appeared fine.

However, again on first boot, the kernel issued a slew of errors, mostly
about not being able to access /proc (which was there). Then, again, after
a reboot, I was OK except that one file /sbin/uname was bad again and
needed to be fixed and replaced.

I suppose I will try and see if I can tar up the reiser3 partition and
restore it in a separate action.

If you require additional information, please let me know.

-- 
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via 
jabber: pete4abw at jabber.org
ICQ: 73676357

Re: reiser4 corruption on initial copy

[David Masover]

Peter wrote:

> 2) I did run badblocks on the dest, and it was clean. 3) I am using the
> patch from 2.6.17.3 and in my kernel, I have full preempt and cfq
> scheduling.

What about the kernel on the livecd?

Re: reiser4 corruption on initial copy

[Peter]

On Fri, 01 Sep 2006 17:35:29 -0500, David Masover wrote:

> Peter wrote:
> 
>> 2) I did run badblocks on the dest, and it was clean. 3) I am using the
>> patch from 2.6.17.3 and in my kernel, I have full preempt and cfq
>> scheduling.
> 
> What about the kernel on the livecd?


Anticipatory
Voluntary

Plus, it is smp, so there are some additional options checked. Should I
have preempt=none with reiser4?

-- 
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via 
jabber: pete4abw at jabber.org
ICQ: 73676357

Re: reiser4 corruption on initial copy

[David Masover]

Peter wrote:
> On Fri, 01 Sep 2006 17:35:29 -0500, David Masover wrote:
> 
>> Peter wrote:
>>
>>> 2) I did run badblocks on the dest, and it was clean. 3) I am using the
>>> patch from 2.6.17.3 and in my kernel, I have full preempt and cfq
>>> scheduling.
>> What about the kernel on the livecd?
> 
> 
> Anticipatory
> Voluntary

Yes, that should be fine, but I was wondering if it's the same version, 
if you built it yourself, etc etc.

> Plus, it is smp, so there are some additional options checked. Should I
> have preempt=none with reiser4?

I'm not sure.

Re: reiser4 corruption on initial copy

[Peter]

On Fri, 01 Sep 2006 11:02:58 +0000, Peter wrote:

> I recently copied over my / partition from a reiserfs to a reiser4
> partition. This may be user error, but I wanted to report it anyway.
> 
> Booting off a live cd- I did the following.
> 
snip...

I was able to duplicate the problem. Apparently, the Sabayon live cd does
not unmount locally mounted partitions. Thus, the reiser4 partitions are
unclean. When I boot up to the newly created and copied partition, I get
the errors I referred to earlier. By manually umounting the partitions I
create or copy from -- including /tmp partitions or /var partitions. I do
not get the boot time errors.

HTH

-- 
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via 
jabber: pete4abw at jabber.org
ICQ: 73676357

Re: reiser4 corruption on initial copy

[Vladimir V. Saveliev]

hello

On Monday 04 September 2006 18:32, Peter wrote:
> On Fri, 01 Sep 2006 11:02:58 +0000, Peter wrote:
> > I recently copied over my / partition from a reiserfs to a reiser4
> > partition. This may be user error, but I wanted to report it anyway.
> >
> > Booting off a live cd- I did the following.
>
> snip...
>
> I was able to duplicate the problem. Apparently, the Sabayon live cd does
> not unmount locally mounted partitions. 

That should not be a problem if sync is called after copy is completed.

It looks like Sabayon live cd even does not care to call sync on reboot.

> Thus, the reiser4 partitions are 
> unclean. When I boot up to the newly created and copied partition, I get
> the errors I referred to earlier. By manually umounting the partitions I
> create or copy from -- including /tmp partitions or /var partitions. I do
> not get the boot time errors.
>

Re: reiser4 corruption on initial copy

[Peter]

On Tue, 05 Sep 2006 13:30:54 +0400, Vladimir V. Saveliev wrote:

> hello
> 
> On Monday 04 September 2006 18:32, Peter wrote:
>> On Fri, 01 Sep 2006 11:02:58 +0000, Peter wrote:
>> > I recently copied over my / partition from a reiserfs to a reiser4
>> > partition. This may be user error, but I wanted to report it anyway.
>> >
>> > Booting off a live cd- I did the following.
>>
>> snip...
>>
>> I was able to duplicate the problem. Apparently, the Sabayon live cd does
>> not unmount locally mounted partitions. 
> 
> That should not be a problem if sync is called after copy is completed.
> 
> It looks like Sabayon live cd even does not care to call sync on reboot.
> 

which clearly explains a lot of the headaches I had when creating or
moving partitions from w/in it!

I'll forward this thread to upstream.

-- 
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via 
jabber: pete4abw at jabber.org
ICQ: 73676357