From: Chris Jensen <cjensen@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Saving files from full failing volume
Date: Sat, 20 Aug 2005 17:22:11 +1000 [thread overview]
Message-ID: <fa61edfd0508200022235af787@mail.gmail.com> (raw)
Hi,
I've just had a disk die, and when I replace it I'm thinking of
setting up LVM, however I'm wondering how the same scenario would pan
out under LVM:
The disk was 160GB and completely full. On thursday the disk reported
a smart error, so I started transferring data off the disk, but seeing
as how I didn't have another 160GB handy, I had to simply copy
directory by directory to vairous bits of scattered space that I was
able to find, starting with the most important data. (the disk then
completely died after getting about half the data off :-( )
If this disk had been setup with LVM, the filesystem on it would've
spanned that disk and an 80G disk (also close to full). Under LVM
would it have been possible to determine which files were being stored
on the 160G so I could use filesystem tools to move them off before
shrinking the volume and moving it entirely to the 80G disk?
(I've read up about LVM and understand I can replace failed
blocks/disks with /dev/zero, so the shrinking and moving part doesn't
worry me to much, it's just the identifying of where files live that
I'm curious about.)
Thanks for any responses
Chris
next reply other threads:[~2005-08-20 7:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 7:22 Chris Jensen [this message]
2005-08-23 14:18 ` [linux-lvm] Saving files from full failing volume Eric M. Hopper
2005-08-27 13:00 ` Chris Jensen
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=fa61edfd0508200022235af787@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.