From: Luca Berra <bluca@comedia.it>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM and sw RAID1
Date: Thu, 24 Aug 2000 20:04:38 +0200 [thread overview]
Message-ID: <20000824200438.A32379@colombina.comedia.it> (raw)
In-Reply-To: <200008241747.e7OHlNd04033@webber.adilger.net>; from adilger@turbolinux.com on Thu, Aug 24, 2000 at 11:47:23AM -0600
On Thu, Aug 24, 2000 at 11:47:23AM -0600, Andreas Dilger wrote:
> Luca Berra write:
> > anyway i found the bug, well there is more than one preventing you to use
> > raid and LVM,
>
> Can you send your fixes to the list? At least then everyone else doesn't
> need to fix the same bugs. It would be even better if Heinz made a new
> bugfix release, but I watch the list for fixes anyways...
Andreas _please_ read my emails
i said that my fix was trashed due to fs failure, i will post it to
the list as soon as i write it again.
i posted what i remembered, tomorrow i dun't have to work so i will look
into it.
i also watch for fixes, i even made a nice big patch encmpassing
everithing that went on the list, sadly it was on a reiserfs fs.
> > fixed that and pvmoved everything onto my lvm+raid5 (fixing another bug
> > in the process). Well, i discovered that reiserfs + LVM + raid DOES NOT
> > WORK, it actually filled 95% of my files with zeroes :)
>
> No journalling filesystem will work properly with RAID 5 - not reiserfs
> and not ext3. You need to stick with a non-journalling filesystem, or
> use RAID1. It may be that this is supposed to be fixed in 2.4, but I'm
> not 100% sure...
>
I probably dinna specify but it i am running 2.4.0-test7pre5
so i can confirm reiserfs not working on raid+lvm with 2.4
AFAIR the problem with journaling and raid was due to raid's usage
of the buffer cache during recnstruction, there was no reconstrucion
happening on my system. i will also try reiserfs on raid without
lvm, i cannot try ext3 since there isn't any patch for 2.4
L.
--
Luca Berra -- bluca@comedia.it
Communication Media & Services S.r.l.
next prev parent reply other threads:[~2000-08-24 18:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-23 20:29 [linux-lvm] LVM and sw RAID1 Peter Green
2000-08-23 22:00 ` Andreas Dilger
2000-08-23 23:48 ` Peter Green
2000-08-24 0:02 ` Andreas Dilger
2000-08-24 2:43 ` Peter Green
2000-08-24 18:58 ` Andreas Dilger
2000-08-24 9:19 ` Nils Juergens
2000-08-24 11:59 ` Peter Green
2000-08-24 12:30 ` Peter Green
2000-08-24 13:39 ` Luca Berra
2000-08-24 19:00 ` Nils Juergens
2000-08-24 10:46 ` Luca Berra
2000-08-24 17:47 ` Andreas Dilger
2000-08-24 18:04 ` Luca Berra [this message]
2000-08-24 22:46 ` Ragnar Kjørstad
2000-08-26 0:39 ` Peter Green
2000-09-01 12:33 ` Jan Niehusmann
2000-09-01 12:35 ` Peter Green
-- strict thread matches above, loose matches on Subject: below --
2000-08-24 0:45 Andreas Dilger
2000-08-24 10:37 Peter.Wuestefeld
2000-08-24 11:57 ` Peter Green
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=20000824200438.A32379@colombina.comedia.it \
--to=bluca@comedia.it \
--cc=adilger@turbolinux.com \
--cc=linux-lvm@msede.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox