I had a working .config. Unfortunately, I left it at office.
The main 'trap' usually would be the SCSI Driver.
If you're using PVSCSI, go into SCSI RAID, then SCSI Low Level
Driver, then select VMware PVSCSI as built-in, not module.
Do you know which one workstation uses? AFAICT there's
On Saturday 09 April 2011 02:02:06 Allan Gottlieb wrote:
On Fri, Apr 08 2011, Mick wrote:
On Friday 08 April 2011 19:51:10 Kevin O'Gorman wrote:
I run that manually once in a while, but regularly clean a bunch of
other things with a script I call cleanup,
-#!/bin/bash
-
On 2011-04-09, Adam Carter adamcart...@gmail.com wrote:
I had a working .config. Unfortunately, I left it at office.
The main 'trap' usually would be the SCSI Driver.
If you're using PVSCSI, go into SCSI RAID, then SCSI Low Level
Driver, then select VMware PVSCSI as built-in, not module.
On Fri, 08 Apr 2011 18:36:28 -0500, Dale wrote:
A little time saver, if you have only one VG, set $LVM_VG_NAME to its
name and you can leave the VG name out of any lv* commands.
I'll have more than one before long so may as well learn the long way.
Neat to know tho. I'm hoping for about
On Fri, 08 Apr 2011 21:02:06 -0400, Allan Gottlieb wrote:
The last one is now an option in /etc/make.conf under FEATURES:
fixlafiles
This sounds great! Outside of some extra time in emerging is there any
reason *not* to add fixlafiles to FEATURES?
Yes, it's already in FEATURES by
On Sat, 9 Apr 2011 17:02:14 +1000, Adam Carter wrote:
If you're using PVSCSI, go into SCSI RAID, then SCSI Low Level
Driver, then select VMware PVSCSI as built-in, not module.
Do you know which one workstation uses? AFAICT there's no option to
choose which controller is presented to
On Saturday 09 April 2011 09:52:01 Neil Bothwick wrote:
No matter how many drives you have, I doubt you'll need more than one
volume group.
...although I did find not long ago that a second VG for another, temporary
distro kept things tidy.. This is not to contradict you though.
--
Rgds
On Sat, 9 Apr 2011 10:43:12 +0100, Peter Humphrey wrote:
No matter how many drives you have, I doubt you'll need more than one
volume group.
...although I did find not long ago that a second VG for another,
temporary distro kept things tidy.. This is not to contradict you
though.
Oh
4/8/2011, Vincent Launchbury vinc...@doublecreations.com вы писали:
On 2011/04/08 02:40PM, Alexey Mishustin wrote:
For example, I don't understand what does -15.15 mean (in default value
%4C %Z %{%b %d} %-15.15L (%4l) %s )
The -15.15 is the same as the printf(3) format.
That's it. I had read
Neil Bothwick wrote:
On Fri, 08 Apr 2011 18:36:28 -0500, Dale wrote:
A little time saver, if you have only one VG, set $LVM_VG_NAME to its
name and you can leave the VG name out of any lv* commands.
I'll have more than one before long so may as well learn the long way.
Neat to
Neil Bothwick wrote:
On Sat, 9 Apr 2011 10:43:12 +0100, Peter Humphrey wrote:
No matter how many drives you have, I doubt you'll need more than one
volume group.
...although I did find not long ago that a second VG for another,
temporary distro kept things tidy.. This is not to
Dale wrote:
Neil Bothwick wrote:
On Sat, 9 Apr 2011 10:43:12 +0100, Peter Humphrey wrote:
No matter how many drives you have, I doubt you'll need more than one
volume group.
...although I did find not long ago that a second VG for another,
temporary distro kept things tidy.. This is not to
Apparently, though unproven, at 12:48 on Saturday 09 April 2011, Dale did
opine thusly:
the new drive ready for LVM. What command adds it to the VG? Is it
vgcreate with some option? I was sort of looking for something like
vgadd or something but no luck finding that. Maybe I am
On Sat, Apr 09 2011, Neil Bothwick wrote:
On Fri, 08 Apr 2011 21:02:06 -0400, Allan Gottlieb wrote:
The last one is now an option in /etc/make.conf under FEATURES:
fixlafiles
This sounds great! Outside of some extra time in emerging is there any
reason *not* to add fixlafiles to
Alan McKinnon wrote:
Apparently, though unproven, at 12:48 on Saturday 09 April 2011, Dale did
opine thusly:
Yes.
PVs, VGs, LVs all have a concept of extend|resize|reduce. What that means
depends on what you are working with, but they all make the thing bigger or
smaller.
For a PV it means the
Neil Bothwick wrote:
On Fri, 08 Apr 2011 21:02:06 -0400, Allan Gottlieb wrote:
The last one is now an option in /etc/make.conf under FEATURES:
fixlafiles
This sounds great! Outside of some extra time in emerging is there any
reason *not* to add fixlafiles to FEATURES?
Yes,
On Friday 08 April 2011 16:30:03 Dale wrote:
J. Roeleveld wrote:
On Fri, April 8, 2011 11:01 pm, Dale wrote:
root@fireball / #
I'm still trying to figure out how the naming part works tho. Now to
mount it and put something on it. See if it works.
Naming part, there are 2 ways of
On Saturday 09 April 2011 00:28:20 Dale wrote:
OK. I learned something. Check this out:
root@fireball / # df
Filesystem 1K-blocks Used Available Use% Mounted on
SNIP
/dev/mapper/sdb--vg-test
51606140 48910048 74652 100% /mnt/temp
On Saturday 09 April 2011 06:43:25 Dale wrote:
Alan McKinnon wrote:
Apparently, though unproven, at 12:48 on Saturday 09 April 2011, Dale
did
opine thusly:
Yes.
PVs, VGs, LVs all have a concept of extend|resize|reduce. What that
means
depends on what you are working with, but
Joost Roeleveld wrote:
On Friday 08 April 2011 16:30:03 Dale wrote:
The naming I was talking about was sort of like a label. I wanted to
use test, where I might use say data in real use, but ended up with this:
root@fireball / # df
Filesystem 1K-blocks Used Available Use%
Joost Roeleveld wrote:
Nice :)
Btw, instead of specifying final size after resizing, you can actually tell
it to add 20GB by doing:
lvrextend -L+20G /dev/sdb-vg/test
--
Joost
So that was what the howto meant. If I know the total I need then I can
specify it but if I know the amount
On Sat, 09 Apr 2011 07:14:52 -0500, Dale wrote:
Mine is set in features too. Thing is, I don't have lafilefixer
installed. I guess portage would say something about broken links if
it was needed. Right?
You don't need lafilefixer with a recent portage, it does the job itself.
--
Neil
Apparently, though unproven, at 13:43 on Saturday 09 April 2011, Dale did
opine thusly:
So, when I get me a new drive, I use pvcreate to get it ready for LVM,
then use vgextend to add it to the VG, then it is available for whatever
LV I want to extend or to make a new LV?
Yup, that's
On Sat, 09 Apr 2011 08:00:49 -0500, Dale wrote:
I wish it was like file system labels but I guess any clues is better
than nothing.
It is like filesystem labels in that you can give VGs and LVs meaningful
names. You can use filesystem labels too, if you feel the need. A logical
volume is just
Joost Roeleveld wrote:
On Saturday 09 April 2011 06:43:25 Dale wrote:
Alan McKinnon wrote:
Apparently, though unproven, at 12:48 on Saturday 09 April 2011, Dale
did
opine thusly:
Yes.
PVs, VGs, LVs all have a concept of extend|resize|reduce. What that
means
depends on what you are
on 04/09/2011 04:33 PM Dale wrote the following:
snip
I'm just needing to find me a good LARGE drive to put in here. I'm
checking out the reviews but it just seems most have issues.
snip
Thoughts?
I think you should be safe with WD1002FAEX, WD1502FAEX and WD2002FAEX.
On Sat, Apr 9, 2011 at 6:33 AM, Dale rdalek1...@gmail.com wrote:
SNIP
I think I am too. Since folks know I am disabled anyway, I went to the Dr
the other day. The new meds aren't perfect but it is better. When I go
back, he may change it to another med. He just wanted to try this first.
On Saturday 09 April 2011 08:04:19 Dale wrote:
Joost Roeleveld wrote:
Nice :)
Btw, instead of specifying final size after resizing, you can actually
tell it to add 20GB by doing:
lvrextend -L+20G /dev/sdb-vg/test
--
Joost
So that was what the howto meant. If I know the total
Hello list,
I've seen some discussion of hard disks on this list recently, but I didn't
notice any reference to Samsung Spinpoint F3 disks.
I have two of these in my workstation; if I were thinking of adding 3 more to
make a more robust system, what advice would I receive?
--
Rgds
Peter
On Sat, Apr 9, 2011 at 1:00 PM, Peter Humphrey pe...@humphrey.ukfsn.org wrote:
Hello list,
I've seen some discussion of hard disks on this list recently, but I didn't
notice any reference to Samsung Spinpoint F3 disks.
I have two of these in my workstation; if I were thinking of adding 3
On Apr 8, 2011 11:13 PM, Pandu Poluan pa...@poluan.info wrote:
I had a working .config. Unfortunately, I left it at office.
The main 'trap' usually would be the SCSI Driver.
If you're using PVSCSI, go into SCSI RAID, then SCSI Low Level
Driver, then select VMware PVSCSI as built-in, not
On 2011-04-10, James Wall wallservi...@gmail.com wrote:
On Apr 8, 2011 11:13 PM, Pandu Poluan pa...@poluan.info wrote:
I had a working .config. Unfortunately, I left it at office.
The main 'trap' usually would be the SCSI Driver.
If you're using PVSCSI, go into SCSI RAID, then SCSI Low
32 matches
Mail list logo
