Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The problem is a corrupted rpm database, mostly coming into existence because of an aborted update process. It also happens sometimes when the package containing rpm itself is updated.
The solution is to delete and then rebuild the database:
The common fix is to delete the rpm databases and run rebuilddb, like
Hope that helps
The result is here.
Quote:
[root@maestro Documents]# yum clean all
error: db3 error(22) from dbenv->open: Invalid argument
error: cannot open Packages index using db3 - Invalid argument (22)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main:
Error: rpmdb open failed
[root@maestro Documents]# rm -f /var/lib/rpm/__db*
[root@maestro Documents]# rpm --rebuilddb
error: failed to create directory /var/lib/rpmrebuilddb.2843: No space left on device
[root@maestro Documents]# yum update
rpmdb: write: 0x1394b30, 8192: No space left on device
Bus error
eklavya/
The result is here.
Quote:
[root@maestro Documents]# rpm --quiet -qa
rpmdb: write: 0x1f9cac0, 8192: No space left on device
Bus error
Did you check for the availability of free disk space on the filesystem where /var is hosted. While installing/updating, yum caches downloaded files to /var/cache/yum directory. If enough space is not available in /var filesystem, then yum will fail.
Did you check for the availability of free disk space on the filesystem where /var is hosted. While installing/updating, yum caches downloaded files to /var/cache/yum directory. If enough space is not available in /var filesystem, then yum will fail.
How to check for the availability of free disk space on the filesystem?
There you go, out of 26GB, your '/' file system has '0' space available and has been used full 100%. If you have no dedicated filesystem for /var, then /var is hosted in /
Delete some unwanted files anywhere in '/' filesystem to make room for yum to cache downloaded files.
I've found out my problem. I've copied 30G hdd which is installed Scientific Linux to 250G hdd. Then I got this sturcture of hdd as attached. I have 218G free space.
Please let me know how to include this free space into LVM.
You can follow these steps. Here I'll assume you want add available free space(218 gb) to existing Logical Volume '/dev/mapper/vg_maestro-lv_root'
Step 1: Make a partition and mark that partition as 0x8e from available free space.
Code:
# fdisk /dev/sda
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4):3
First cylinder....: <ENTER>
Last cylinder.....: <ENTER>
Command (m for help): t
Partition number (1-4): 3
Hex code (type L to list codes): 8e
Command (m for help): w
Device Boot Start End Blocks Id System
/dev/sda1 * 1 64 512000 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 64 3917 30944256 8e Linux LVM
/dev/sda3 3918 30401 212732730 3 XENIX usr
/dev/sda4 3917 3917 6022+ 83 Linux
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.