From: "Peter" <sw98234-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
To: reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org
Subject: reiser4 corruption on initial copy
Date: Fri, 1 Sep 2006 11:02:58 +0000 (UTC) [thread overview]
Message-ID: <ed9412$2r9$1@sea.gmane.org> (raw)
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
next reply other threads:[~2006-09-01 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 11:02 Peter [this message]
2006-09-01 15:24 ` reiser4 corruption on initial copy Peter
2006-09-01 22:35 ` David Masover
2006-09-02 10:26 ` Peter
2006-09-02 18:27 ` David Masover
2006-09-04 14:32 ` Peter
2006-09-05 9:30 ` Vladimir V. Saveliev
2006-09-05 18:53 ` Peter
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='ed9412$2r9$1@sea.gmane.org' \
--to=sw98234-pkbjnfxxiarbdgjk7y7tuq@public.gmane.org \
--cc=reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.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.