search for: logvol04

...kages index using db3 - No space left on device (28) error: cannot open Packages database in /var/lib/rpm Traceback (most recent call last): <...> # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol01 5.0G 3.6G 1.2G 76% /var /dev/mapper/VolGroup00-LogVol04 1008M 456M 501M 48% /var/log /dev/mapper/VolGroup00-web 4.9G 140M 4.5G 3% /var/www # mount /dev/mapper/VolGroup00-LogVol01 on /var type ext3 (rw) /dev/mapper/VolGroup00-LogVol04 on /var/log type ext3 (rw) /dev/mapper/VolGroup00-web on /var/www type ext3 (rw) # touch /var/test touch...

...this list, and I'm having troubles because a lack of disk on my Raid 5. The server have a LVM system on the Raid 5 and the partitions on LVM is ext3. I can't identify where the ext3 superblock is on this LVM partition to use the fsck. I've tried many ways: fsck -b 8192 /dev/VolGroup/LogVol04 dumpe2fs /dev/VolGroup/LogVol04 | grep -i superblock I tried to use the testdisk, and nothing of these solves my problem, i need to recover the files from an ext3 partition or repair this partition, what sounds better to me. Can anyone helps me? []'s -- Davi Santos Oliveira --------------...

...d. This is the file system layout. /etc/fstab /dev/mapper/vg_voinet01-lv_root / ext4 defaults 1 1 UUID=302ab0fo-f985-4903-86e2-e218b1345e0 /boot ext4 defaults 1 2 /dev/mapper/vg_voinet01-lv_home /home ext4 defaults 1 2 /dev/mapper/vg_voinet01-LogVol04 /var ext4 defaults 1 2 /dev/mapper/vg_voinet01-lv_log /var/log ext4 defaults 1 2 /dev/mapper/vg_voinet01-lv_spool /var/spool ext4 defaults 1 2 /dev/mapper/vg_voinet01-lv_swap swap swap defaults 0 0 tmpfs...

...Mounted on /dev/mapper/VolGroup00-LogVol00 2.0G 368M 1.6G 20% / /dev/sda1 61M 24M 35M 41% /boot /dev/mapper/VolGroup00-LogVol05 19G 11G 7.6G 58% /data01 none 7.9G 0 7.9G 0% /dev/shm /dev/mapper/VolGroup00-LogVol04 2.0G 53M 1.9G 3% /tmp /dev/mapper/VolGroup00-LogVol02 3.0G 1.8G 1.1G 64% /usr /dev/mapper/VolGroup00-LogVol03 2.0G 94M 1.8G 5% /var /dev/mapper/VolGroup01-u01 148G 93M 141G 1% /u01 /dev/sdc...

...gt; xfs_fsr /raid/Temp/someDiskimage.iso extents before:101 after:3 DONE > xfs_bmap /raid/Temp/someDiskimage.iso [output shows 3 extents and 1 hole] and now comes the bummer: i wanted to check the fragmentation of the whole filesystem (just for checking): > xfs_db -r /dev/mapper/VolGroup00-LogVol04 xfs_db: unexpected XFS SB magic number 0x00000000 xfs_db: read failed: Invalid argument xfs_db: data size check failed cache_node_purge: refcount was 1, not zero (node=0x2a25c20) xfs_db: cannot read root inode (22) THAT output was definitly not there when I did this the last time and therefor the...

...s = yes log level = 3 admin users = @"Domain Admins" [finance] comment = finance dept path = /home/finance valid users = @Finance browseable = yes nt acl support = yes force group = Finance admin users = @"Domain Admins" My fstab for my /home slice looks like: /dev/VolGroup00/LogVol04 /home ext3 acl 1 2 ldd smbd yields: libldap-2.2.so.7 => /usr/lib/libldap-2.2.so.7 (0x00df5000) liblber-2.2.so.7 => /usr/lib/liblber-2.2.so.7 (0x00111000) libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x0011d000) libkrb5.s...

...received the following error: checking filesystems /dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000 blocks /dev/sda1: clean, 47/120016 files, 80115/512000 blocks /dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks /dev/mapper/vg_voinet01-LogVol04: clean, 770219/20480000 files, 34881086/8102000 blocks fsck.ext4: Bad magic number in super-block while trying to open /dev/mapper/vg_voinet01-lv_log /dev/mapper/vg_voinet01-lv_log The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really...

...s = yes log level = 3 admin users = @"Domain Admins" [finance] comment = finance dept path = /home/finance valid users = @Finance browseable = yes nt acl support = yes force group = Finance admin users = @"Domain Admins" My fstab for my /home slice looks like: /dev/VolGroup00/LogVol04 /home ext3 acl 1 2 ldd smbd yields: libldap-2.2.so.7 => /usr/lib/libldap-2.2.so.7 (0x00df5000) liblber-2.2.so.7 => /usr/lib/liblber-2.2.so.7 (0x00111000) libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x0011d000) libkrb5.s...

...03 /home ext3 defaults 1 2 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 /dev/VolGroup00/LogVol02 /tmp ext3 defaults 1 2 /dev/VolGroup00/LogVol04 /var/log ext3 defaults 1 2 /dev/VolGroup00/LogVol05 /var/www ext3 defaults 1 2 /dev/VolGroup00/LogVol01 swap swap defaults 0 0 >From the logs I gather that the device is sda1 Jul 2 16:42:45 inet02 kernel: SCSI devi...

Hello, I'm in a slightly unusual situation and I'd really appreciate some advice. I installed CentOS 5.2 on a server about a month ago. Today I happened to check the 'free' command and noticed that the Swap line reads as follows: Swap: 0 0 0 I'm pretty certain that when I installed the OS and created a custom partition table, that I defined a