From: Christian <evilninja@gmx.net>
To: reiserfs-list@namesys.com
Cc: Nicolae Mihalache <mache@abcpages.com>
Subject: Re: corrupted files
Date: Sat, 09 Apr 2005 15:00:59 +0200 [thread overview]
Message-ID: <4257D20B.3030302@gmx.net> (raw)
In-Reply-To: <425704EA.7020707@abcpages.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nicolae Mihalache wrote:
> Hi,
>
> I have experience some weird problems on a reiserfs partition. I tried
> to copy a big archive (6.9GB) from another computer using scp or ftp and
> it seems that the file gets somehow corrupted. Right now I manage to
> reproduce the problem even locally, I copy the file in the same
> directory, no error, still cmp tells they are different:
when does the corruption kicks in? are small plaintext files also
corrupted? or only if you copy files of a certain amount of filesize?
if textfiles are also affacted, maybe "diff" could show us exactly *what*
differs.
> It may be a hardware problem but I somehow doubt it.
/var/log/messages?
> reiserfsck says No corruptions found.
> The system is SuSE 9.0, kernel 2.4.21-273-smp4G (it is a dell poweredge
so, this is reiserfs3, right? did you use the current reiserfsprogs?
- --
BOFH excuse #44:
bank holiday - system operating credits not recharged
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCV9ILC/PVm5+NVoYRArPRAKCs1j03hvHYZEKe7lj/EsjdRJJzKwCfXHP7
AgI7gi5wd8ZWKKFeIV8r774=
=NPxg
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-04-09 13:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 22:25 corrupted files Nicolae Mihalache
2005-04-09 13:00 ` Christian [this message]
2005-04-09 18:04 ` Nicolae Mihalache
2005-04-09 19:16 ` Linuxhippy
2005-04-10 18:50 ` Nicolae Mihalache
-- strict thread matches above, loose matches on Subject: below --
2014-09-09 15:21 Corrupted files Leslie Rhorer
2014-09-09 15:50 ` Sean Caron
2014-09-09 16:03 ` Sean Caron
2014-09-09 22:24 ` Eric Sandeen
2014-09-09 22:57 ` Sean Caron
2014-09-10 1:00 ` Roger Willcocks
2014-09-10 1:23 ` Leslie Rhorer
2014-09-10 5:09 ` Eric Sandeen
2014-09-10 0:48 ` Leslie Rhorer
2014-09-10 1:10 ` Roger Willcocks
2014-09-10 1:31 ` Leslie Rhorer
2014-09-10 14:24 ` Emmanuel Florac
2014-09-10 14:49 ` Sean Caron
2014-09-09 16:08 ` Emmanuel Florac
2014-09-09 22:06 ` Dave Chinner
2014-09-10 1:12 ` Leslie Rhorer
2014-09-10 1:25 ` Sean Caron
2014-09-10 1:43 ` Leslie Rhorer
2014-09-10 14:31 ` Emmanuel Florac
2014-09-10 14:52 ` Grozdan
2014-09-10 15:12 ` Emmanuel Florac
2014-09-10 15:32 ` Grozdan
2014-09-10 14:54 ` Sean Caron
2014-09-10 23:18 ` Leslie Rhorer
2014-09-11 13:24 ` Greg Freemyer
2014-09-12 7:06 ` Emmanuel Florac
2014-09-10 1:53 ` Dave Chinner
2014-09-10 3:10 ` Leslie Rhorer
2014-09-10 3:33 ` Dave Chinner
2014-09-10 4:14 ` Leslie Rhorer
2014-09-10 4:22 ` Leslie Rhorer
2014-09-10 14:34 ` Emmanuel Florac
2014-09-10 4:51 ` Leslie Rhorer
2014-09-10 5:23 ` Dave Chinner
2014-09-11 5:47 ` Leslie Rhorer
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=4257D20B.3030302@gmx.net \
--to=evilninja@gmx.net \
--cc=mache@abcpages.com \
--cc=reiserfs-list@namesys.com \
/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.