All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Jensen <cjensen@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Saving files from full failing volume
Date: Sat, 27 Aug 2005 23:00:49 +1000	[thread overview]
Message-ID: <fa61edfd05082706007d36d221@mail.gmail.com> (raw)
In-Reply-To: <1124806695.17889.22.camel@bats.omnifarious.org>

> The only way to really identify where files live in LVM is to identify
> which filesystem they're on.  Then they might end up being on any random
> block of that filesystem.  You can identify which physical extents a
> particular filesystem is using easily, but not which physical extents a
> particular file is using.
> 
> Perhaps someone else can correct me if I'm wrong about this, but as I
> understand things this is how it works.

Thanks for the response Eric. Let me check that I understand this correctly:
 If I were to use LVM to create a file system that spans 2 hard disks,
of capacity 80G each (for simplicities sake), giving a total capacity
of 160G, if that filesystem grows to (say) 100G and then one of the
disks begins to fail, there is no way for me to backup the files that
would be endangered, short of backing up the entire 100G, to another
disk entirely.

Is there a better way I should go about organising my disks and LVM so
that surviving a hard disk failure is not so difficult?

  reply	other threads:[~2005-08-27 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-20  7:22 [linux-lvm] Saving files from full failing volume Chris Jensen
2005-08-23 14:18 ` Eric M. Hopper
2005-08-27 13:00   ` Chris Jensen [this message]
2005-08-27 14:58     ` Fredrik Tolf
2005-08-27 16:41       ` Dan Pritts
2005-08-28  0:47       ` Chris Jensen
2005-08-28  1:47         ` Fredrik Tolf

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=fa61edfd05082706007d36d221@mail.gmail.com \
    --to=cjensen@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 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.