Linux LVM users
 help / color / mirror / Atom feed
From: Tracy R Reed <treed@copilotconsulting.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] massive LV corruption
Date: Mon, 13 Sep 2004 17:46:07 -0700	[thread overview]
Message-ID: <20040914004607.GB9253@copilotconsulting.com> (raw)
In-Reply-To: <20040911110830.GC32306@copilotconsulting.com>

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

On Sat, Sep 11, 2004 at 04:08:30AM -0700, Tracy R Reed spake thusly:
> I am running Fedora Core 1 with stock RedHat kernel 2.4.22-1.2188.nptl. I
> filled my /usr/local to 100% and decided I needed some more space so I ran
> the lvextend and resize_reiserfs commands like I have done many times

Nobody has an opinion to offer? I've been a big fan of LVM for ages but
this incident has really shaken my confidence in it. It is my
understanding that all of the software I am using should be pretty solid
by now. I am hesitatnt to allow LVM operations on production systems
anymore if this sort of thing can happen without explanation. :( I would
like to think I did something wrong but I've used lvextend and
resize_reiserfs a number of times before on other machines without
incident.

-- 
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 --]

  parent reply	other threads:[~2004-09-14  0:56 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 [this message]
2004-09-14  5:45   ` Clint Byrum
2004-09-14 12:45     ` Tracy R Reed
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=20040914004607.GB9253@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox