Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
At my school we (a bunch of Linux-newbies) set up an Ubuntu(Debian) box for filesharing and printserver. And it works like a charm.
-Until a harddrive died...
/hda is the system-disk,
/hdb and /hdc are put together in a LVM-group and mounted as /home for user files and filesharing.
But /hdb is seriously unstable and tends to go dead within a day or two..
-So it needs to be thrown out, and a nother one installet. Yes, but what about the data ?
There is room enough on /hdc for all our data but the LVM-group is allocated 'Non-contiguous' -whatever that means....
you need to migrate the data of off /dev/hdb to do this you the following command assuming here that partition /dev/hdb1 is being used in the lvm setup and that you have enough space on your other physical volumes. run
pvmove /dev/hdb1
which will ensure that none of your lvm data is still stored on it
then you run
vgreduce vg0 /dev/hdb1
where vg0 is the name of your volume group (you can get this info from vgdisplay) this will remove partition /dev/hdb1 from that volume group if all goes well you can then remove you faulty drive
-----------
root@3e:~ # pvdisplay /dev/hdb1
--- Physical volume ---
PV Name /dev/hdb1
VG Name lager
PV Size 19,16 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 4905
Free PE 0
Allocated PE 4905
PV UUID iwKrdc-k1RA-cHhz-kzc4-q90U-Qe1o-HF6oTS
-------------
root@3e:~ # pvdisplay /dev/hdc1
--- Physical volume ---
PV Name /dev/hdc1
VG Name lager
PV Size 37,28 GB / not usable 0
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 9543
Free PE 0
Allocated PE 9543
PV UUID 48MiUC-d6Zl-J4XL-AMhx-3A1o-foMY-rxEWpg
-------------
root@3e:~ # pvmove /dev/hdb1
No extents available for allocation
------------
root@3e:~ # vgreduce lager /dev/hdb1
Physical volume "/dev/hdb1" still in use
-----------
I even tried to do it in Webmin
----------
Failed to remove physical volume :
File descriptor 8 left open
File descriptor 9 left open
No extents available for allocation
-----------
I don't get it......
According to the HOWTO that should do the trick, but my box refuses...
The entire VG was formatted as reiserfs after creation, if that the reason ?
I tried to use [resize_reiserfs], but I can't umount /home (VG mounted as /home).
>root@3e:~ # pvmove /dev/hdb1
>No extents available for allocation
This appears to be your problem, you have no more room in your volume group, take a look at the output from vgdisplay.
You may need to add in more physical volumes if you do not have enough extents available.
When you have enough room left in your volume group pvmove will work fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.