All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tracy R Reed <treed@copilotconsulting.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] massive LV corruption
Date: Tue, 14 Sep 2004 05:45:40 -0700	[thread overview]
Message-ID: <20040914124540.GA13649@copilotconsulting.com> (raw)
In-Reply-To: <58B212CA-0611-11D9-BB02-000A95730E92@spamaps.org>

[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]

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 were
hosed. The LVM/block layer should prevent resize_reiserfs or any part of
reiserfs from damaging the lv's. I love reiser and have used it with great
success for years. I find it sad that people still pan reiserfs after all
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 it.
I have a feeling it is going to do for Linux what MS claims WinFS will
(someday) do for their OS.

> 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 2.6.something
(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.

-- 
Tracy Reed                     The attachment is a digital signature.
http://copilotconsulting.com   More info: http://copilotconsulting.com/sig

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-14 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 11:08 [linux-lvm] massive LV corruption Tracy R Reed
2004-09-11 11:25 ` Tracy R Reed
2004-09-14  0:46 ` Tracy R Reed
2004-09-14  5:45   ` Clint Byrum
2004-09-14 12:45     ` Tracy R Reed [this message]
2004-09-14 14:49       ` Clint Byrum
2004-09-14 20:06         ` Tracy R Reed
2004-09-14 20:41           ` Clint Byrum

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=20040914124540.GA13649@copilotconsulting.com \
    --to=treed@copilotconsulting.com \
    --cc=linux-lvm@redhat.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.