Red Hat Bugzilla – Bug 250029
lost ls command in bash
Last modified: 2013-02-28 23:05:49 EST
Description of problem:
I cannot use ls command on a current version of bash
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enter ls command
-bash: ls: command not found
It should display the list of file and directory
What is the current value of $PATH? Are the other commands in the coreutils
/root/bin: Aucun fichier ou répertoire de ce type (No such file or directory)
What changed in between 'ls' working and 'ls' not working? Did you install
something, upgrade something, etc?
What does 'rpm -q coreutils' say?
(In reply to comment #3)
> What changed in between 'ls' working and 'ls' not working? Did you install
> something, upgrade something, etc?
Not at all. The information I haven't added is the LVM somehow crashed at boot
and automatically use the fsck to recover. Since then, some of essential command
are missing and I just find out vi is missing as well.
> What does 'rpm -q coreutils' say?
#rpm -q coreutils
Sounds like an lvm2 recovery problem then. Reassigning.
Please attach important system information
- exact description what happened ("the LVM somehow crashed" is not enough :)
- which commands you entered befeore crash
- syslog messages
Didn't you changed some block device (i.e. change size of partition without
correctly resizing filesystem ang logical volume first, remove some device
without properly deactivating lvm, etc...) ?
- I booted the system normally when the LVM went into recovery mode and it
prompted me to fix using the default setting. After the full recovery, RHGB
booted normally. After logging, I used the terminal for listing files and
directory when I noticed some of bash command like "ls" were no longer there.
- No commands before the crash, I shut down the system and restarted.
- Unfortunately I have reinstalled Fedora 7 after backup and neglected to save
the syslog messages =(
- I have not modified the LVM. The hard driver that Fedora 7 uses suddenly
stopped . After checking the problem and correct it, I started Fedora 7 when the
There is not enough information to investigate what happened.
LVM has no recovery mode during boot - it is filesystem check. What caused
corruption on filesystem is not clear here but LVM was activated correctly (if
there is problem, LV is not activated and fsck cannot be run on it).
Closing this bug, if you hit this again, please reopen it and attach requested