On 01/23/2009 11:28 AM, Mike Castle wrote:
On Wed, Jan 21, 2009 at 8:13 PM, Ron Johnson <ron.l.john...@cox.net> wrote:
If I have lots of existing data in JBODs, would I create a PV and VG on the
new drive, mv all the data from the existing drives to the new VG, then add
my existing drives (while also enlarging the fs) to the one-drive VG, thus
making an uber-device?
That is how I started and how I've been, more or less, running with
LVM for years, though I think I'm about to change.
Over an 8 hour period, I grew my lv from one device to 4, resizing
an ext4 fs each time.
Note that I'm running 2.6.28 from:
deb http://kernel-archive.buildserver.net/debian-kernel trunk main
[snip]
One pain point I have is this: In order to run resize2fs(8), you have
to fsck the FS first. As they grow larger and larger, this takes
longer and longer. I have a 2TB FS now that I really don't want to
grow any more because of that.
Ext4 may solve the fscking issue, but in the one article I've read so
Yup, it does!!! (The required version of e2fsprogs is in Sid,
probably in Lenny, and probably isn't in Etch.)
# df -TH /data/big
Filesystem Type Size Used Avail Use% Mounted on
/dev/dm-0 ext4 3.0T 1.4T 1.5T 48% /data/big
# umount -v /data/big
/dev/dm-0 umounted
# time e2fsck -pfC0 /dev/main_huge_vg/main_huge_lv
/dev/main_huge_vg/main_huge_lv: 515937/180412416 files
(1.9% non-contiguous), 333951921/721649664 blocks
real 3m10.506s
user 2m21.589s
sys 0m4.020s
far, resizing wasn't mentioned in it. (I'm also considering ext4 for
other reasons.)
One thing I do tend to do with every disk is this:
I put a small swap partition on each disk, then the rest is an LVM
Stuffing your mobo with *dirt-cheap* RAM is the other way to solve
this particular problem!!!
[big snip]
--
Ron Johnson, Jr.
Jefferson LA USA
"I am not surprised, for we live long and are celebrated poopers."
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
