On Sun, Nov 20, 2011 at 2:32 PM, Dale wrote:
> James Wall wrote:
>>
>> On Thu, Nov 17, 2011 at 11:18 PM, Dale wrote:
>>>
>>> Is there a way to make this work? I googled but I couldn't find anything
>>> on
>>> this one. Well, a few worthless hits that just happen to have the words
>>> on
>>> the
On Thu, 24 Nov 2011 04:48:28 -0600, Dale wrote:
> umount /data
> e2fsck -f /dev/mapper/data-data1
> resize2fs /dev/mapper/data-data1 400G
> lvreduce -L 400G /dev/data/data1
> pvmove -v /dev/sdb1
I feel safer reducing the filesystem to smaller than the intended
partition/LV size, just in case, and
Dale wrote:
So, the commands is something like this:
resize2fs /dev/mapper/data-data1 400G < this should make the VG a
absolute size of 400Gbs which leaves a little room left over. If I
used a - in front, it would reduce by that amount. >
lvreduce -L 400G /dev/data/data1 < I assume I can make
On Wed, 23 Nov 2011 21:28:56 -0600
Dale wrote:
> Dale wrote:
> > Neil Bothwick wrote:
> >> You have space in the filesystem, but the volume containing that
> >> filesystem is too large to move. You must first reduce the
> >> filesystem size, with resize2fs or whatever suits your fs, then
> >> sh
Alex Schuster wrote:
Dale asks:
OK. Everyone duck, I been thinking on this and Neils info above. lol
This is what I sort of figured out and tell me where I am off here. I
have to reduce the file system, change the partition in cfdisk (?),
resize the lv, then reduce the vg, then I can run pvm
Dale asks:
> OK. Everyone duck, I been thinking on this and Neils info above. lol
> This is what I sort of figured out and tell me where I am off here. I
> have to reduce the file system, change the partition in cfdisk (?),
> resize the lv, then reduce the vg, then I can run pvmove? After
Dale wrote:
Neil Bothwick wrote:
You have space in the filesystem, but the volume containing that
filesystem is too large to move. You must first reduce the filesystem
size, with resize2fs or whatever suits your fs, then shrink the LV
with lvresize. That will free up enough extents to be able
Neil Bothwick wrote:
You have space in the filesystem, but the volume containing that
filesystem is too large to move. You must first reduce the filesystem
size, with resize2fs or whatever suits your fs, then shrink the LV
with lvresize. That will free up enough extents to be able to fit them
On Wed, 23 Nov 2011 13:07:55 -0600, Dale wrote:
> I think we have a problem:
>
> root@fireball / # pvmove -v /dev/sdb1
> Finding volume group "data"
> Archiving volume group "data" metadata (seqno 4).
> Creating logical volume pvmove0
> Moving 59604 extents of logical volume d
Neil Bothwick wrote:
On Tue, 22 Nov 2011 23:50:08 -0600, Dale wrote:
Another LVM question. If I want to remove a drive and tell pvmove to
move the data off it, can the drive have files being written to it
while this is done? I'm wanting to use my old spare drive to move some
things around but
On Tue, 22 Nov 2011 23:50:08 -0600, Dale wrote:
> Another LVM question. If I want to remove a drive and tell pvmove to
> move the data off it, can the drive have files being written to it
> while this is done? I'm wanting to use my old spare drive to move some
> things around but right now LVM
Another LVM question. If I want to remove a drive and tell pvmove to
move the data off it, can the drive have files being written to it while
this is done? I'm wanting to use my old spare drive to move some things
around but right now LVM has it. I think it is OK but just want to make
sure.
James Wall wrote:
On Thu, Nov 17, 2011 at 11:18 PM, Dale wrote:
Is there a way to make this work? I googled but I couldn't find anything on
this one. Well, a few worthless hits that just happen to have the words on
the same page for some reason.
Look for /dev/dm-0 to monitor your lvm partiti
Neil Bothwick wrote:
On Thu, 17 Nov 2011 11:37:59 -0600, Dale wrote:
Also, this will only work if the VG has sufficient unused space (eg.
not used by LVs) on the other disk(s) to accomodate the data moved.
Thanks. Clear as mud now. lol I'm getting there. Is there a tool
to see if there is
On Thu, 17 Nov 2011 11:37:59 -0600, Dale wrote:
> > Also, this will only work if the VG has sufficient unused space (eg.
> > not used by LVs) on the other disk(s) to accomodate the data moved.
> Thanks. Clear as mud now. lol I'm getting there. Is there a tool
> to see if there is enough room
Joost Roeleveld wrote:
On Thursday, November 17, 2011 10:43:28 AM Florian Philipp wrote:
Am 17.11.2011 07:50, schrieb Dale:
[...]
One more question. I have two drives. A 250Gb and a 750Gb. Originally
the data was on the 750Gb drive. I set the 250Gb up on LVM then moved
things over from the
On Thursday, November 17, 2011 10:43:28 AM Florian Philipp wrote:
> Am 17.11.2011 07:50, schrieb Dale:
> [...]
>
> > One more question. I have two drives. A 250Gb and a 750Gb. Originally
> > the data was on the 750Gb drive. I set the 250Gb up on LVM then moved
> > things over from the 750Gb.
Am 17.11.2011 07:50, schrieb Dale:
[...]
> One more question. I have two drives. A 250Gb and a 750Gb. Originally
> the data was on the 750Gb drive. I set the 250Gb up on LVM then moved
> things over from the 750Gb. I then added the 750Gb to the VG and
> resized the file system. So, in theory
Manuel McLure wrote:
You should be able to use e2label (or "tune2fs -L" as I do) on the
/dev/data/data1 device to set the filesystem label. That's the logical
volume that the operating system needs to mount. # tune2fs -L mylabel
/dev/data/data1 should do what you need. I haven't done this with
On Wed, Nov 16, 2011 at 6:52 PM, Dale wrote:
> OK. I jumped into LVM. I took my spare drive, put it to use with LVM.
> Then copied data from my super large drive to it and backed up some to DVDs
> that wouldn't fit. Then I put the big drive on LVM and put the stuff back.
> Now comes the probl
OK. I jumped into LVM. I took my spare drive, put it to use with LVM.
Then copied data from my super large drive to it and backed up some to
DVDs that wouldn't fit. Then I put the big drive on LVM and put the
stuff back. Now comes the problem. I use LABELS in fstab and would
like to conti
21 matches
Mail list logo
