From: "Stéphane Jourdois" <kwisatz@rubis.org>
To: reiserfs-list@namesys.com
Subject: [Fwd: Re: Data being corrupted on reiserfs 3.6]
Date: Mon, 16 Jan 2006 21:04:14 +0100 [thread overview]
Message-ID: <43CBFC3E.2040900@rubis.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 289 bytes --]
Same excuses for forgetting CC: on first post.
--
/// Stephane Jourdois /"\ ASCII RIBBON CAMPAIGN \\\
((( Consultant securite \ / AGAINST HTML MAIL )))
\\\ 24 rue Cauchy X ///
\\\ 75015 Paris / \ +33 6 8643 3085 ///
[-- Attachment #2: Re: Data being corrupted on reiserfs 3.6 --]
[-- Type: message/rfc822, Size: 1644 bytes --]
From: "Stéphane Jourdois" <kwisatz@rubis.org>
To: Michael Barnwell <xterminate@xterminate.me.uk>
Subject: Re: Data being corrupted on reiserfs 3.6
Date: Sun, 15 Jan 2006 11:05:56 +0100
Message-ID: <43CA1E84.3060807@rubis.org>
Michael Barnwell a écrit :
> Is it just a problem with reisferfs and RAID 5 do you know? I can't
> really afford a hardware RAID 5 controller, so using ext3 maybe more
> sensible for me.
It seems to occur only with reiserfs over raid5. Other filesystems seems
to be less vulnerable.
It must be a raid5 issue, because I never had a problem using reiserfs
on a real disk.
I saw several reports like yours, I reported this myself one year ago,
and I don't know if raid guys
investigated this issue.
You could try to reproduce the problem without reiserfs, using dd on the
raid5 device without any filesystem. This for sure would tie the problem
with raid5 and could help debugging this problem. I know that reiserfs
tends to write very fast, and observed this issue only when copying
large files.
Sorry for the bad news.
--
/// Stephane Jourdois /"\ ASCII RIBBON CAMPAIGN \\\
((( Consultant securite \ / AGAINST HTML MAIL )))
\\\ 24 rue Cauchy X ///
\\\ 75015 Paris / \ +33 6 8643 3085 ///
next reply other threads:[~2006-01-16 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 20:04 Stéphane Jourdois [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-16 20:03 [Fwd: Re: Data being corrupted on reiserfs 3.6] Stéphane Jourdois
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=43CBFC3E.2040900@rubis.org \
--to=kwisatz@rubis.org \
--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.