. This computer is giving me fits because the home directory is overloaded.
[bobg@box9 ~]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_box9-lv_root 46703584 8460264 35870920 20% / tmpfs 1543956 388 1543568 1% /dev/shm /dev/sdc2 495844 66800 403444 15% /boot /dev/mapper/vg_box9-lv_home 45251640 42600112 352856 100% /home 192.168.1.48:/mnt/rfg/ 721061760 40920288 643513664 6% /mnt/srvr1 192.168.1.48:/mnt/glg/ 721061760 40920288 643513664 6% /mnt/srvr2
There are 3 hard drives, apparently only one is being used, /dev/sdc, a 40 gig drive shared with a Windows partition. There are also 2 80 gig drives, one has nothing on it but an LVM partiton:
Disk /dev/sdb: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders, total 156250000 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xd0f4738c
Device Boot Start End Blocks Id System /dev/sdb1 2048 156248063 78123008 8e Linux LVM
How do I get /dev/sdb1 added to the system?
This is probably the result of swapping drives from a defunct computer into this one several months ago. I have been telling myself that I'll just do a new install when F-15 comes out but it looks like I need to fix the problem now.
What do I need to do?
Bob
On Thu, May 5, 2011 at 1:45 PM, Bob Goodwin bobgoodwin@wildblue.net wrote:
. This computer is giving me fits because the home directory is overloaded.
[bobg@box9 ~]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_box9-lv_root 46703584 8460264 35870920 20% / tmpfs 1543956 388 1543568 1% /dev/shm /dev/sdc2 495844 66800 403444 15% /boot /dev/mapper/vg_box9-lv_home 45251640 42600112 352856 100% /home 192.168.1.48:/mnt/rfg/ 721061760 40920288 643513664 6% /mnt/srvr1 192.168.1.48:/mnt/glg/ 721061760 40920288 643513664 6% /mnt/srvr2
There are 3 hard drives, apparently only one is being used, /dev/sdc, a 40 gig drive shared with a Windows partition. There are also 2 80 gig drives, one has nothing on it but an LVM partiton:
Disk /dev/sdb: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders, total 156250000 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xd0f4738c
Device Boot Start End Blocks Id System /dev/sdb1 2048 156248063 78123008 8e Linux LVM
How do I get /dev/sdb1 added to the system?
This is probably the result of swapping drives from a defunct computer into this one several months ago. I have been telling myself that I'll just do a new install when F-15 comes out but it looks like I need to fix the problem now.
What do I need to do?
Of course there's about 50 ways to do something about this but as long as you don't care about data reliabilty, the easiest thing would be to make the 80gb drive part of your existing "vg_box9" volume group. Add some of all of the extents to your "lv_home" logical volume and then resize your partition to fill the LV.
Keep in mind, if one of the two drives go bad you'll probably loose all of /home so caveat emptor applies.
The 80gb LVM drive may or may not already have a volume group (VG) associated with it, if so you might have to add "-f" to vgextend.
First you need to add /dev/sb1 to your volume group, i.e.:
vgextend -f vg_box9 /dev/sdb1
but I would try without the -f first and see if it complains.
Then you need to expand your "lv_home" logical volume over /dev/sdb1.
lvextend /dev/vg_box9/lv_home /dev/sdb1
This is a short cut to have lv_home use all of /dev/sdb1, usually you would have to tell it how much of the vg you want to use but if you specify the device it uses all of it.
If your brave enough to let it call resizefs for you, add the '-r' option.
You didn't say what the underlying file system is so you need to know if it supports online resizing or not. If not then you need to boot a live CD/USB stick although going into single user mode would probably let you unmount /home as well.
I hope this helps but as usual, no warranty on the results and be sure to backup anything critical.
Richard
On 05/05/11 15:12, Richard Shaw wrote:
On Thu, May 5, 2011 at 1:45 PM, Bob Goodwinbobgoodwin@wildblue.net wrote:
. This computer is giving me fits because the home directory is overloaded.
[bobg@box9 ~]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_box9-lv_root 46703584 8460264 35870920 20% / tmpfs 1543956 388 1543568 1% /dev/shm /dev/sdc2 495844 66800 403444 15% /boot /dev/mapper/vg_box9-lv_home 45251640 42600112 352856 100% /home 192.168.1.48:/mnt/rfg/ 721061760 40920288 643513664 6% /mnt/srvr1 192.168.1.48:/mnt/glg/ 721061760 40920288 643513664 6% /mnt/srvr2There are 3 hard drives, apparently only one is being used, /dev/sdc, a 40 gig drive shared with a Windows partition. There are also 2 80 gig drives, one has nothing on it but an LVM partiton:
Disk /dev/sdb: 80.0 GB, 80000000000 bytes 255 heads, 63 sectors/track, 9726 cylinders, total 156250000 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xd0f4738c Device Boot Start End Blocks Id System /dev/sdb1 2048 156248063 78123008 8e Linux LVMHow do I get /dev/sdb1 added to the system?
This is probably the result of swapping drives from a defunct computer into this one several months ago. I have been telling myself that I'll just do a new install when F-15 comes out but it looks like I need to fix the problem now.
What do I need to do?
Of course there's about 50 ways to do something about this but as long as you don't care about data reliabilty, the easiest thing would be to make the 80gb drive part of your existing "vg_box9" volume group. Add some of all of the extents to your "lv_home" logical volume and then resize your partition to fill the LV.
Keep in mind, if one of the two drives go bad you'll probably loose all of /home so caveat emptor applies.
The 80gb LVM drive may or may not already have a volume group (VG) associated with it, if so you might have to add "-f" to vgextend.
First you need to add /dev/sb1 to your volume group, i.e.:
vgextend -f vg_box9 /dev/sdb1
but I would try without the -f first and see if it complains.
[root@box9 ~]# vgextend vg_box9 /dev/sdb1 Physical volume '/dev/sdb1' is already in volume group 'vg_box9' Unable to add physical volume '/dev/sdb1' to volume group 'vg_box9'.
Then you need to expand your "lv_home" logical volume over /dev/sdb1.
lvextend /dev/vg_box9/lv_home /dev/sdb1
This is a short cut to have lv_home use all of /dev/sdb1, usually you would have to tell it how much of the vg you want to use but if you specify the device it uses all of it.
[root@box9 ~]# lvextend /dev/vg_box9/lv_home /dev/sdb1 No free extents on physical volume "/dev/sdb1" No specified PVs have space available
What is this telling me? Fdisk shows it as an empty drive.
Thanks for the help.
Bob
If your brave enough to let it call resizefs for you, add the '-r' option.
You didn't say what the underlying file system is so you need to know if it supports online resizing or not. If not then you need to boot a live CD/USB stick although going into single user mode would probably let you unmount /home as well.
I hope this helps but as usual, no warranty on the results and be sure to backup anything critical.
Richard
On Thu, May 5, 2011 at 2:30 PM, Bob Goodwin bobgoodwin@wildblue.net wrote:
[root@box9 ~]# vgextend vg_box9 /dev/sdb1 Physical volume '/dev/sdb1' is already in volume group 'vg_box9' Unable to add physical volume '/dev/sdb1' to volume group 'vg_box9'.
Then you need to expand your "lv_home" logical volume over /dev/sdb1.
lvextend /dev/vg_box9/lv_home /dev/sdb1
This is a short cut to have lv_home use all of /dev/sdb1, usually you would have to tell it how much of the vg you want to use but if you specify the device it uses all of it.
[root@box9 ~]# lvextend /dev/vg_box9/lv_home /dev/sdb1 No free extents on physical volume "/dev/sdb1" No specified PVs have space available
What is this telling me? Fdisk shows it as an empty drive.
That's what I was afraid of. /dev/sb1 is already in use. Fdisk doesn't really know anything about LVM (other than the partition label). You need to inspect the output of vgdisplay and lvdisplay to see what's going on. You may not actually have an unused drive available to expand /home.
Another graphical way to explore your disks is the "palimpsest" utility, which from the menu is just called "Disk Utility".
Richard
Richard
On 05/05/11 16:14, Richard Shaw wrote:
That's what I was afraid of. /dev/sb1 is already in use. Fdisk doesn't really know anything about LVM (other than the partition label). You need to inspect the output of vgdisplay and lvdisplay to see what's going on. You may not actually have an unused drive available to expand /home.
Yes, I've been looking there and lvm> pvdisplay shows all three drive full. But full with what? This is a terrible system, there's no way to know what's "filling" those drives! I don't believe they are full of my data. I was considering unplugging two of them to see how the system acts? But that's a hell of a way to troubleshoot a software problem it seems to me.
I will probably have to move files on to my NFS server until I can rework the whole mess when I'm ready to install F-15.
Bob
Another graphical way to explore your disks is the "palimpsest" utility, which from the menu is just called "Disk Utility".
Richard
Richard
On Thu, May 5, 2011 at 4:21 PM, Bob Goodwin bobgoodwin@wildblue.net wrote:
On 05/05/11 16:14, Richard Shaw wrote:
That's what I was afraid of. /dev/sb1 is already in use. Fdisk doesn't really know anything about LVM (other than the partition label). You need to inspect the output of vgdisplay and lvdisplay to see what's going on. You may not actually have an unused drive available to expand /home.
Yes, I've been looking there and lvm> pvdisplay shows all three drive full. But full with what? This is a terrible system, there's no way to know what's "filling" those drives! I don't believe they are full of my data. I was considering unplugging two of them to see how the system acts? But that's a hell of a way to troubleshoot a software problem it seems to me.
I will probably have to move files on to my NFS server until I can rework the whole mess when I'm ready to install F-15.
Well {pv,vg,lv}display will give you an idea to the structure of your storage environment (drives, partitions, volumes, etc), not if the file system is full.
One command I use frequently is "du" or disk usage. The most useful way I've found to use it is like this:
du -h --max-depth=1
This is nice because one you know who the biggest culprits of disk usage you can cd into the directory and then run the exact same command again (use the up arrow to browse your history) and follow the trail.
There's a graphical version that's more interactive as well.
You may have some weird log file or something else that was growing out of control for some reason. Either of those methods should help you find it.
Good luck, Richard
On 05/05/11 17:35, Richard Shaw wrote:
On Thu, May 5, 2011 at 4:21 PM, Bob Goodwinbobgoodwin@wildblue.net wrote:
On 05/05/11 16:14, Richard Shaw wrote:
That's what I was afraid of. /dev/sb1 is already in use. Fdisk doesn't really know anything about LVM (other than the partition label). You need to inspect the output of vgdisplay and lvdisplay to see what's going on. You may not actually have an unused drive available to expand /home.
Yes, I've been looking there and lvm> pvdisplay shows all three drive full. But full with what? This is a terrible system, there's no way to know what's "filling" those drives! I don't believe they are full of my data. I was considering unplugging two of them to see how the system acts? But that's a hell of a way to troubleshoot a software problem it seems to me. I will probably have to move files on to my NFS server until I can rework the whole mess when I'm ready to install F-15.Well {pv,vg,lv}display will give you an idea to the structure of your storage environment (drives, partitions, volumes, etc), not if the file system is full.
This is what I see and it seems to be saying these two drives are full?
--- Physical volume --- PV Name /dev/sdc3 VG Name vg_box9 PV Size 19.05 GiB / not usable 15.00 MiB Allocatable yes (but full) PE Size 32.00 MiB Total PE 609 Free PE 0 Allocated PE 609 PV UUID lZVB91-QMK0-mER5-m3Yy-2D2X-8XWy-yS6AQn
--- Physical volume --- PV Name /dev/sdb1 VG Name vg_box9 PV Size 74.50 GiB / not usable 4.00 MiB Allocatable yes (but full) PE Size 32.00 MiB Total PE 2384 Free PE 0 Allocated PE 2384 PV UUID SC73uG-gs6q-axub-eX0L-j4Sj-fH9o-7H4h1C
One command I use frequently is "du" or disk usage. The most useful way I've found to use it is like this:
du -h --max-depth=1
Yes I use du -h often.
I've got a lot of large files in a Downloads directory. I'm copying them to another drive and I hope that will free up enough space to carry me through for a couple of months or whenever I am ready to re-install the system.
Thanks, you have been very helpful, got me pointed in the right direction I believe.
Bob
This is nice because one you know who the biggest culprits of disk usage you can cd into the directory and then run the exact same command again (use the up arrow to browse your history) and follow the trail.
There's a graphical version that's more interactive as well.
You may have some weird log file or something else that was growing out of control for some reason. Either of those methods should help you find it.
Good luck, Richard
Hi Bob,
Maybe some more information will help.
Looks like /dev/mapper/vg_box9-lv_root is 47GB and /dev/mapper/vg_box9-lv_home is 45GB /dev/sdb1 is 78GB total which is under the 92GB reported for the vg_box9 so it has to be on another drive already.
Your /boot is on /dev/sdc2. Is that drive the 40gb that is shared with Windows?
So what is on /dev/sda? Can you give us the output of fdisk -l, pvs, vgs and lvs? Seems to me you have at least 60GB hiding somewhere.
--- Will Y.
On 09/05/11 17:56, aragonx@dcsnow.com wrote:
Hi Bob,
Maybe some more information will help.
Looks like /dev/mapper/vg_box9-lv_root is 47GB and /dev/mapper/vg_box9-lv_home is 45GB /dev/sdb1 is 78GB total which is under the 92GB reported for the vg_box9 so it has to be on another drive already.
Your /boot is on /dev/sdc2. Is that drive the 40gb that is shared with Windows?
So what is on /dev/sda? Can you give us the output of fdisk -l, pvs, vgs and lvs? Seems to me you have at least 60GB hiding somewhere.
Will Y.
I've got things working again. I found that files I deleted were apparently retained in /home/bobg/.local/share/Trash. I cleaned that out and df showed home at 60%, dropped from 100%. Not sure why that happened but it's good for now.
I have ordered a larger drive which I should have in a day or two and that will replace at least two of the existing drives.
Thanks.
Bob
-
Bob Goodwin -
Richard Shaw -
Will Yonker