Re: [gentoo-user] Re: experience with rsnapshot

2011-11-24 Thread covici
Grant Edwards grant.b.edwa...@gmail.com wrote:

 On 2011-11-24, cov...@ccs.covici.com cov...@ccs.covici.com wrote:
 
  I am using rdiff-backup which is no longer maintained, but still seems
  to work, but I was thinking to use rsnapshot instead which seems like a
  nice way to do this, but this seems not to have been maintained for a
  while, either, so I was wondering if anyone is using it and how it works
  for you?
 
 I set up rsnapshot a few months ago, and so far it seems to be working
 fine.  I found the documentation about how to configure the intervals
 and schedule the jobs to be a bit confusing, but once the light bulb
 went on, it's pretty easy.


Thanks, this is what I was wondering about.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici
 cov...@ccs.covici.com



Re: [gentoo-user] glibc-2.14.1 upgrade

2011-11-24 Thread justin
On 24/11/11 06:27, Paul Hartman wrote:
 Hi,
 
 After emerging glibc-2.14.1 today, pam stopped working, which
 prevented KDE from working and some other things. I got this kind of
 message:
 
 /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
 /lib64/libcrypt.so.1)
 
 There were no @preserved-rebuild and revdep-rebuild found nothing. I
 rebuilt pam and things seem to be working again. Are there any other
 packages I should rebuild before encountering a problem? Or some way
 to detect which need to be rebuilt? Should I re-emerge world against
 my new glibc? :)
 
 Thanks,
 Paul
 

Hi Paul,

after an glibc upgrade it is time to do an

emerge -e system world


This is what binary distros actually do when they have major bumps in
their releases.

Justin



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-user] LVM and LABELS in fstab

2011-11-24 Thread Alan McKinnon
On Wed, 23 Nov 2011 21:28:56 -0600
Dale rdalek1...@gmail.com 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
  shrink the LV with lvresize. That will free up enough extents to
  be able to fit them all on one disk. Look at the output from lvs
  to see what is taking up all the space. 
 
  So, me staring at it a while and trying to figure it out did work.  
  That is what I was thinking.  Thing is, it looks to me like it
  would just move the stuff over then I can reduce it by what sdb is
  making for its share.  Although, their way makes sense too.
 
  I basically need to reduce the thing by 59604 PEs then it can move 
  them over to sdc so I can remove sdb.  Looks like I am about to
  really learn something here.  It uses ext4 by the way.  Looks like
  adding is easier than removing, sort of.
 
  Now to get my ducks in a row.  o_O
 
  Thanks.
 
  Dale
 
  :-)  :-)
 
 
 
 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 all that, I can remove the drive sdb?  Do I have the
 order correct too?  If it does involve all this, I'm not sure I want
 to do this.  The file system and cfdisk part makes me nervous.  Maybe
 some of this isn't needed and I am reading some of the info
 incorrectly, I hope.

No, not quite. You're on the right track but got some of the details
wrong. Let's look first at the layers of stuff involved:


   files  directories

   file system

   logical volume (LV)

   volume group (VG)

   physical volume (PV)  

   physical partition(i.e. /dev/sda1 etc)

   physical disk (i.e. something Seagate etc made)



OK, there's a lot of stuff there. When you made the LV, you worked from
the bottom up. To undo it, you work from the top down. And the
important bit:

Everything in that list only knows about the one directly below it.

The other important bit:

Nothing in that list can be bigger than the thing below it.

This makes perfect sense: You can't store a 5G file on a 4G
file-system, nor can you create a 1TB partition on a 500G disk.


Tools like lv* only know about LVs and how they are built, it's
clueless about the actual files and filesystems involved. So when you
want to move things around, the tool will look at the volume and see
how many extents it uses. It will want to move all those extents
somewhere else.

Now say you made a 40G filesystem on an LV but only have 500M of
actual files on it. LVM tools are going to want to move a 40G volume,
never mind that 39.5G of it is unused. If you don't have 40G of free
space, you have to start juggling.

First get the filesystem down to a reasonable size:

1. Shrink the filesystem using resize2fs, resize_reiserfs etc.
2. lvreduce to make the logical volume match the file system.

Now you have a 500M thing to move around and your life gets easier.

What you want to accomplish is to move all the LVs from one disk to
another disk, you need to have enough free space on the new PV to hold
all those LVs. When you've done that the old PV will now have no data
on it (none of it's extents will be in use), you can remove it from the
VG, then delete the PV, and finally remove the disk from the machine.

*fdisk is the only truly destructive tool in your toolbox, the LVM
tools will all give you errors if you try and remove things that are in
use or if there's not enough free space.

There's no easy recipes for this that you can just follow. You need to
understand the things you are dealing with and know what they are. But
it's not *that* hard.

Like most things in Linux, LVM assumes that you, Dale, are probably not
a complete idiot and that you do know what you are doing. That's why
are the gory details are exposed for you to play with.

Now if it were Windows and you were extremely lucky, you might get a
GUI thingy that let's you drag an bunch of unnamed stuff from here and
put it there. Which would promptly fail, silently.





-- 
Alan McKinnnon
alan.mckin...@gmail.com



Re: [gentoo-user] Process to resize ext3 file system at the command line?

2011-11-24 Thread J. Roeleveld
On Fri, November 18, 2011 1:33 am, Mark Knecht wrote:
 On Thu, Nov 17, 2011 at 4:21 PM, Neil Bothwick n...@digimed.co.uk wrote:
 On Thu, 17 Nov 2011 16:13:09 -0800, Mark Knecht wrote:

  Do you have separately partitioned drives with those partitions
  arranged into single-partition arrays, or do you have one RAID device
  that is then partitioned?
 
  If the latter, you should certainly work with the md device.
 
  I prefer to avoid all this confusion by creating a large, single
  partition array that I use an an LVM physical volume.

 Separately partitioned drives arranged into RAID arrays.

 So you have three partitions arranged into a single RAID5 partition,
 say /dev/md1?

 In that case, the size of /dev/md1 should already be correct and you
 only
 need to resize the filesystem and you should ignore my witterings about
 fdisk that filed to take into account your use of RAID.
 resize2fs /dev/md1 should be all you need, you shouldn't even need to
 unmount the filesystem.


 I have 3 partitions which were previously RAID-1. I've already failed
 one drive so at this moment it's a 2-drive RAID-1. I'm attempting to
 get those two remaining 2 partitions converted to RAID-5 the command
 suggested on the RAID list for doing that isn't working for me.

 Once the 250GB RAID-1 is converted to RAID-5 i have to add a new drive
 back in to become a 3-drive RAID-5. The drive I add will be the drive
 I just failed.

 c2stable ~ # mdadm --grow /dev/md6 --level=5
 mdadm: /dev/md6: could not set level to raid5
 c2stable ~ #

 c2stable ~ # mdadm -D /dev/md6
 /dev/md6:
Version : 1.1
  Creation Time : Thu Apr 15 10:45:35 2010
 Raid Level : raid1
 Array Size : 247416933 (235.96 GiB 253.35 GB)
  Used Dev Size : 247416933 (235.96 GiB 253.35 GB)
   Raid Devices : 2
  Total Devices : 2
Persistence : Superblock is persistent

Update Time : Thu Nov 17 13:27:20 2011
  State : clean
  Active Devices : 2
 Working Devices : 2
  Failed Devices : 0
  Spare Devices : 0

   Name : c2stable:6  (local to host c2stable)
   UUID : 249c7331:a8203540:c8f3b020:fb30a66b
 Events : 1039

Number   Major   Minor   RaidDevice State
   0   860  active sync   /dev/sda6
   1   8   221  active sync   /dev/sdb6
 c2stable ~ #

I have never had to change a RAID-1 to RAID-5, but I would do it as follows:

1) Fail 2 drives from the RAID-1
2) Remove those 2 drives from the RAID-1
3) Create a new RAID-5 (with failed disk) using the 2 removed drives
4) Copy the data over from the RAID-1 to the RAID-5
5) Remove the RAID-1
6) Add the third drive to the RAID-5 and let it rebuild.

I don't know the commands for the above from memory, but I'm sure some of
this is in the man-page.

--
Joost









Re: [gentoo-user] Re: Re: Re: Another hardware thread

2011-11-24 Thread Neil Bothwick
On Thu, 24 Nov 2011 06:22:45 +0100, Stefan G. Weichinger wrote:

  DVI-I outputs may be converted to VGA with a simple adapter; the
  connector at the computer contains both analog and digital
  signaling.  
 
 If there is only one ... this results in one VGA-output only as well ...
 and I need 2.

Is there no on-board video?


-- 
Neil Bothwick

We can sympathize with a child who is afraid of the dark, but the
tragedy of life is that most people are afraid of the light.


signature.asc
Description: PGP signature


Re: [gentoo-user] LVM and LABELS in fstab

2011-11-24 Thread Dale

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 this the same 
size as above? 

pvmove -v /dev/sdb1
pvremove /dev/sdb1



For some poor soul that is as new to LVM as I am.  Here is the commands 
I ended up using:


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 did have to unmount it first.  It just wouldn't proceed without that 
one.  It then told me I had to run fsck on it too.  Other than that, it 
seems to have worked fine.


Now to figure out a few other things.  I may be back.  o_O

Dale

:-)  :-)

--
I am only responsible for what I said ... Not for what you understood or how 
you interpreted my words!




Re: [gentoo-user] Re: Re: Re: Another hardware thread

2011-11-24 Thread Stefan G. Weichinger
Am 24.11.2011 10:53, schrieb Neil Bothwick:

 Is there no on-board video?

Yes, there is.

yesterday: Enabled it, removed the PCIe-card, removed the Do not
remove-covers from the onboard-DVI-connectors 

Unfortunately only one of these brings analog signal, the other one is
DVI-D   so it doesn't have those 4 pins needed for my adapter.

:-(

S



Re: [gentoo-user] Re: Re: Re: Another hardware thread

2011-11-24 Thread Michael Mol
On Thu, Nov 24, 2011 at 6:25 AM, Stefan G. Weichinger li...@xunil.at wrote:
 Am 24.11.2011 10:53, schrieb Neil Bothwick:

 Is there no on-board video?

 Yes, there is.

 yesterday: Enabled it, removed the PCIe-card, removed the Do not
 remove-covers from the onboard-DVI-connectors 

 Unfortunately only one of these brings analog signal, the other one is
 DVI-D   so it doesn't have those 4 pins needed for my adapter.

Is the onboard video of the same chipset as your video card? If so,
you should be able to run them just fine at the same time. I once had
an onboard ATI chipset (HD3200) working together with a Radeon 5770 to
push five displays--two VGA, two DVI and one HDMI.


-- 
:wq



Re: [gentoo-user] Re: Re: Re: Another hardware thread

2011-11-24 Thread Stefan G. Weichinger
Am 24.11.2011 16:06, schrieb Michael Mol:

 Is the onboard video of the same chipset as your video card? If so,
 you should be able to run them just fine at the same time. I once had
 an onboard ATI chipset (HD3200) working together with a Radeon 5770 to
 push five displays--two VGA, two DVI and one HDMI.

Onboard = on-CPU in this case: core-i7-2600 brings Intel HD3000.
And the video card is a Nvidia GeForce GT530.

I assume that won't work out?

No energy for fiddling today, had a decent server-crash at a customer.
Glad to have my box running with one TFT, at least today :)

thanks, Stefan




Re: [gentoo-user] LVM and LABELS in fstab

2011-11-24 Thread Neil Bothwick
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 resizing it back up after.

resize2fs /dev/mapper/data-data1 390G
lvreduce -L 400G /dev/data/data1
resize2fs /dev/mapper/data-data1

 I did have to unmount it first.  It just wouldn't proceed without that 
 one.  It then told me I had to run fsck on it too.

Those are both from resize2fs, once you have run that, you can remount the
filesystem.


-- 
Neil Bothwick

...and that is how we know the Earth to be banana-shaped.


signature.asc
Description: PGP signature


Re: [gentoo-user] Re: Re: Re: Another hardware thread

2011-11-24 Thread Michael Mol
On Nov 24, 2011 11:33 AM, Stefan G. Weichinger li...@xunil.at wrote:

 Am 24.11.2011 16:06, schrieb Michael Mol:

  Is the onboard video of the same chipset as your video card? If so,
  you should be able to run them just fine at the same time. I once had
  an onboard ATI chipset (HD3200) working together with a Radeon 5770 to
  push five displays--two VGA, two DVI and one HDMI.

 Onboard = on-CPU in this case: core-i7-2600 brings Intel HD3000.
 And the video card is a Nvidia GeForce GT530.

 I assume that won't work out?

 No energy for fiddling today, had a decent server-crash at a customer.
 Glad to have my box running with one TFT, at least today :)

 thanks, Stefan

Never tried mix  match with Intel. I'd say it's worth a try, as long as
you can stay away from the proprietary drivers. Sounds likely you'll be
hunting for a new card, though.
On Nov 24, 2011 11:33 AM, Stefan G. Weichinger li...@xunil.at wrote:

 Am 24.11.2011 16:06, schrieb Michael Mol:

  Is the onboard video of the same chipset as your video card? If so,
  you should be able to run them just fine at the same time. I once had
  an onboard ATI chipset (HD3200) working together with a Radeon 5770 to
  push five displays--two VGA, two DVI and one HDMI.

 Onboard = on-CPU in this case: core-i7-2600 brings Intel HD3000.
 And the video card is a Nvidia GeForce GT530.

 I assume that won't work out?

 No energy for fiddling today, had a decent server-crash at a customer.
 Glad to have my box running with one TFT, at least today :)

 thanks, Stefan





[gentoo-user] Error message for several ebuilds when updating world.

2011-11-24 Thread waltdnes
  I just ran a sync and update on my laptop.  The builds for...

gnome-extra/libgsf-1.14.21
x11-libs/gdk-pixbuf-2.24.0-r1
gnome-base/librsvg-2.34.1-r1
www-client/firefox-7.0.1-r1
app-text/ghostscript-gpl-9.04-r4
app-office/abiword-2.8.6-r1

...all came up with the same warning in /var/log/portage/elog

WARN: prepare
  We've already been run in this tree; you should
  avoid this if possible (perhaps by filing a bug)

Any ideas what this is all about?

-- 
Walter Dnes waltd...@waltdnes.org



Re: [gentoo-user] Error message for several ebuilds when updating world.

2011-11-24 Thread Dale

waltd...@waltdnes.org wrote:

   I just ran a sync and update on my laptop.  The builds for...

gnome-extra/libgsf-1.14.21
x11-libs/gdk-pixbuf-2.24.0-r1
gnome-base/librsvg-2.34.1-r1
www-client/firefox-7.0.1-r1
app-text/ghostscript-gpl-9.04-r4
app-office/abiword-2.8.6-r1

...all came up with the same warning in /var/log/portage/elog

WARN: prepare
   We've already been run in this tree; you should
   avoid this if possible (perhaps by filing a bug)

Any ideas what this is all about?



http://forums.gentoo.org/viewtopic-p-6878530.html?sid=924b3c65e5584c4dc81672583d97b85d#6878530

You need more ram, swap space or maybe drive space for the portage work 
directory.  Basically, it's running out of space somewhere.  Look at 
top maybe and see what it says then df to see if a partition is full 
or really close to it.  Keep in mind, usage may drop after it fails and 
does a little cleaning up.


Hope that helps.

Dale

:-)  :-)

--
I am only responsible for what I said ... Not for what you understood or how 
you interpreted my words!




Re: [gentoo-user] Re: Re: Re: Another hardware thread

2011-11-24 Thread Stefan G. Weichinger
Am 24.11.2011 18:20, schrieb Michael Mol:

 Never tried mix  match with Intel. I'd say it's worth a try, as long as
 you can stay away from the proprietary drivers. Sounds likely you'll be
 hunting for a new card, though.

planning to get into my car after my first coffee ...
thx, greets, Stefan