Red Hat Bugzilla – Bug 504043
when using boot.iso I don't have fsadm
Last modified: 2013-01-10 00:14:18 EST
Description of problem:
When running rescue mode from http://sunsite.mff.cuni.cz/pub/fedora/development/x86_64/os/images/boot.iso (on KVM virtual machine) I tried to run
lvm lvreduce -L -6G -r -v -t /dev/VolGroup00/LogVol00
Executing: fsadm --dry-run --verbose check /dev/VolGroup00/LogVol00
but apparently there is no fsadm on the disk. Which is weird, because there is lvm from the same package lvm2.
Version-Release number of selected component (if applicable):
boot.iso dated 2009-05-31
Steps to Reproduce:
no fsadm, have to run resize2fs manually with calculating number of sectors to shrink (asking for screwing it up); FAIL -- the most important reason for me why to run Rescue Mode is to change size of root LV.
This will be fixed in the next build of anaconda. Thanks for the bug report.
Actually fsadm from F11 doesn't work in busybox (readlink doesn't have -e parameter).
To fix busybox or not to fix busybox (and fix fsadm instead)?
That is the question.
It looks like we have here couple issues - rescue image seems to only contain 'lvm' binary - so there are no symlinks for commands like lvresize, fsadm - so it looks like lvm has some 'special' installation for rescue image - I'm wondering how are dependencies solved in this case?
Should we list binaries we need for lvm to make it operational?
For now it looks like fsadm, lvresize symlink and blockdev command is missing in the rescue image.
The script should be running 'lvm lvresize' not 'lvresize'.
(fix the script to work the same way as lvm_dump.sh)
Script was updated with commit https://www.redhat.com/archives/lvm-devel/2009-June/msg00048.html - new boot.iso will be checked when it will be ready.
busybox readlink fix is at
thanks Denys - patch backported to 1.14.1-2.fc12.