Re: Hangs doing ls -l but not ls
From: Bill Vermillion (bv_at_wjv.com)
Date: 12/02/04
- Next message: NSM: "Re: Logins and serial transfers on same wire"
- Previous message: Boyd Lynn Gerber: "Re: Hangs doing ls -l but not ls"
- In reply to: kevin_at_qantel.com: "Re: Hangs doing ls -l but not ls"
- Next in thread: kevin_at_qantel.com: "Re: Hangs doing ls -l but not ls"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 02 Dec 2004 20:45:01 GMT
In article <1102006202.872637.116840@f14g2000cwb.googlegroups.com>,
<kevin@qantel.com> wrote:
>
>Jean-Pierre Radley wrote:
>> Kevin Coulter typed (on Wed, Dec 01, 2004 at 02:01:35PM -0800):
>> | I've got a customer with 5.0.6, RS506A, OSS646B installed.
>> |
>> | Systems "seems" fine, except cd drive does not work, and sometimes
>> | tape drive does not work. We can boot off of CD without trouble.
>> |
>> | Went poking around: If I am in root, do a "ls" I see the listing.
>If I
>> | do "ls -l" it hangs. Same thing in /dev. Tried redirecting output
>to a
>> | file, no help. Still hangs. When I hang, I have to kill the
>session,
>> | ps still shows it active, kill -9 does not clean it up.
>>
>> What does just 'l' do? And 'ls -bl'?
>>
>> --
>> JP
>Thanks for the help. /etc/passwd and /etc/shadow look ok, running the
>tests as a user instead of root does not seem to matter. lc works, ls
>-x works, "l" hangs (I let it sit for 5 minutes).
"looking ok" and "being ok" are sometimes two different things.
Since ls works and lc works - both of which do NOT query the
password or group file, try ls -n. That will list the
UID and GID of the files.
If that works then it still can be a problem with either password
or group.
Have either the /etc/passwd or the /etc/group file ever been
edited by hand? Are the permissions and ownership correct.
Owned by bin and group owner is auth and only bin and auth
can have write privledges but the final octet must be read only.
If either of those have been edited by hand double check to make
sure there are no blanks lines, or anything extraneous.
Try view /etc/passwd [view is vi in read only mode and you don't
really want to accidentally fire up vi on either of those unless
you know exactly what you are doing]. You can 'list' with
1,$l while in 'view' to see if there are any spurious characters
in the file. Pass it through 'less' if you have a large number
of users.
>What is really bothering me is that after a hang, I disconnect and
>reconnect. My process is still out there (with a parent of 1, the shell
>does die). I cannot kill it.
That is the expected procedure when you disconnect and a program
is hung waiting for something. Since you - the parent - has gone
away - the program becomes and orphan and is adopted by init - aka 1.
>Backups are also getting tape write errors most but not all days. Not
>sure if it is related or not. When it does get the error, it occurs
>during, not the beginning of the backup. The backup is only backing up
>/usr/xxx where xxx has the application and application data in many
>subdirectories underneath that tree. I have no problems doing ls -l,
>etc on that directory. The problem only seems to be with / and /dev.
You might post a few lines from the error log. That might give
a hint as to just what 'xxx' is.
>What started this was we were trying to mount a cdrom, and it hung.
>Booted the machine to a bootable (non UNIX) CD, and it worked fine. So
>I went to look at /dev/cd0, and hung doing an ls -l on that....
What OS was this bootable non Unix CD? I've seen people totally
destroy things by using some MS tools [I use the word "tools"
advisedly] when trying to fix a Unix system. I've found you can
use Unix tools on non-Unix systems [Knoppix is a wonderful recovery
tool even for MS-XP] but the reverse can often do you in.
>What is baffling me is why I can do a "file" on some things in /dev,
>but not others.
And 'some' is not helping a lot either. What files don't responsd
to 'file' and when you do a 'file' on dev is almost everything
a block special or character special?
I don't want to sound picky but details are important when you
aren't sitting at the keyboard.
>So I'm at a point: hardware or software? If software, what can I do
>remotely to fix it - the earliest I can get there to attempt a full
>reload is 2 weeks away. Am I sure that a full reload will fix the
>issues? And finally, what caused this so we don't end up there
>again...
When you say a 'full reload' do you mean a reinstall from the
distribution media, or a from a backup program such as
BackupEdge or LoneTar.
The latter make it easy, and if you have no idea of what the
problem may be - using either of their recovery tools is the best
way and starting with remaking the filesystems completely. That
means if something was torched in some way the new fs will take
care of that. But just a plain reload from tape may leave some
corruption.
>Thanks for the advice so far, and thanks in advance for any help you
>can provide in the future.
The more details the better.
Bill
-- Bill Vermillion - bv @ wjv . com
- Next message: NSM: "Re: Logins and serial transfers on same wire"
- Previous message: Boyd Lynn Gerber: "Re: Hangs doing ls -l but not ls"
- In reply to: kevin_at_qantel.com: "Re: Hangs doing ls -l but not ls"
- Next in thread: kevin_at_qantel.com: "Re: Hangs doing ls -l but not ls"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
