From: "daniel.poelzleithner" <poelzi@poelzi.org>
To: David Greaves <david@dgreaves.com>
Cc: reiserfs-list@namesys.com
Subject: Re: support for Reiserfs 3.6 failed on ~1Tb lvm2 lv on 2.6.6?
Date: Tue, 08 Jun 2004 23:38:05 +0200 [thread overview]
Message-ID: <40C631BD.2050706@poelzi.org> (raw)
In-Reply-To: <40C627B7.9000803@dgreaves.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Greaves wrote:
| Thanks - I'll try both :)
|
| I'm talking to namesys too.
|
| I am wondering if the resync corrupted the data.
|
| I'm pretty happy that I didn't do anything 'wrong' - something is either
| broken in hw (mem) or buggy.
cat /proc/mdstats looks good ?
I had problems with my home server, too. He carries 11 ide harddisks.
Many problems come from bad connections. Look that the power is stable,
not to many harddisks on one power string. Controll your ide cable. I
always use elektrical contact spray to make sure the contacts are good.
I haven't experienced any Problems since then.
The rsync can not corrupt any data as long no device are removed by the
raid system i think.
regards
~ Daniel
- --
nihil me cirumdat
.. . .. ... . . .. . ... . .. . ... . . .
pgp key @ http://files.poelzi.org/pgp.txt
ED80 E53D 5269 4BB1 1E73 3A53 CBF9 A421 0A7B 003D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org
iD8DBQFAxjG9y/mkIQp7AD0RAtqFAJ0elPirndm7GwWMEAc5VZCSk+o2SwCgnusw
bLO4XJ8urlP5MJywyFwQQtk=
=bFIK
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-08 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 19:45 support for Reiserfs 3.6 failed on ~1Tb lvm2 lv on 2.6.6? Burnes, James
2004-06-08 20:55 ` David Greaves
2004-06-08 21:33 ` Bernd Schubert
2004-06-08 21:38 ` daniel.poelzleithner [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-08 16:08 David Greaves
2004-06-08 19:18 ` Bernd Schubert
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=40C631BD.2050706@poelzi.org \
--to=poelzi@poelzi.org \
--cc=david@dgreaves.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.