[linux-lvm] massive LV corruption
cbyrum at spamaps.org
Tue Sep 14 14:49:45 UTC 2004
On Tuesday, September 14, 2004, at 05:45 AM, Tracy R Reed wrote:
> On Mon, Sep 13, 2004 at 10:45:55PM -0700, Clint Byrum spake thusly:
>> I've never used resize_reiserfs, but I do know that a lot of people I
>> talk to won't use ReiserFS because of past problems that have since
>> been fixed. The tools that come with ReiserFS are generally very good.
> I'm pretty sure it can't possibly be reiserfs because the actual lv's
> hosed. The LVM/block layer should prevent resize_reiserfs or any part
> reiserfs from damaging the lv's. I love reiser and have used it with
> success for years. I find it sad that people still pan reiserfs after
Just wanted to say that I don't pan ReiserFS, as I have never had
problems like others did when it was still very new and there were
problems keeping it in sync with the mainline kernel. I don't use
ReiserFS v3 because, while very fast for workstations, it has major
problems with concurrant write accesses.
Hans Reiser has stated that this is because each filesystem has a lock
on it, so while writing to, say, /home/cvs, anybody else who wants to
write to /home/cvs will have to wait. We have a CVS server where the
CVS trees and home dirs are on two seperate logical volumes, and this
locking scheme *HURTS* when two people are trying to do a cvs update.
CVS writes a "read lock" file to each cvs directory, and some temp
files in the working copy. Combine this with vim writing to its "swap"
files all the time.. the box sometimes comes to a screeching halt for
all users for almost a minute as they get in line with the filesystem
That said, this ReiserFS+LVM1 system (redhat 8.0) has never had any
data issues. :-P
> this time. I am really looking forward to reiser4 (released already
> but I
> want to see it get some more time behind it) and some cool plugins for
> I have a feeling it is going to do for Linux what MS claims WinFS will
> (someday) do for their OS.
Yes, bring it on. I plan to convert some workstations to it first..
then home server.. then non critical work servers.. the usual
progression before production.
>> If I had to blame one thing, I'd blame the heavily hacked 2.4 kernel
>> that came with Fedora. :-P
> I suspect this is the case. I am using Fedora Core 2 with a
> (exact kernel version in the typescript file from my original posting)
> kernel and that seems to be the most likely culprit. However, I doubt
> anyone from RedHat is going to take an interest because this isn't
> reproduceable. That is to say, I am not going to trash my box again to
> reproduce it.
You said you were running 2.4.22.nptl or something.
More information about the linux-lvm