From: Wallace Wadge <wwadge@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: lvm + raid (confused)
Date: Wed, 30 Nov 2005 10:08:17 +0100 [thread overview]
Message-ID: <efef33d20511300108y4f6c441vff876085f80f816b@mail.gmail.com> (raw)
In-Reply-To: <efef33d20511292301s1fe5cf0dp90180833f51e2360@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
Perfect! Thanks!
Sadly I cannot extend the filesystem anyway thanks to the installer
defaulting to ext3 so I'm using lvm for almost nothing except snapshots (i.e.
I shouldn't be needing lvcreate/lvextend).
What I was worried was: my fs is definetely on the HW raid (logically), but
I wasn't sure if free blocks would have come from somewhere else.
Anyway this seems to do the trick. Thanks once again.
Wallace
[-- Attachment #2: Type: text/html, Size: 445 bytes --]
prev parent reply other threads:[~2005-11-30 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 7:01 [linux-lvm] lvm + raid (confused) Wallace Wadge
2005-11-30 8:48 ` Heinz Mauelshagen
2005-11-30 9:08 ` Wallace Wadge [this message]
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=efef33d20511300108y4f6c441vff876085f80f816b@mail.gmail.com \
--to=wwadge@gmail.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;
as well as URLs for NNTP newsgroup(s).