Subject: Re: /etc/daily gets stuck
To: None <email@example.com>
From: Paul Mather <firstname.lastname@example.org>
Date: 01/11/2001 10:47:03
On Thu, 11 Jan 2001, Todd Vierling wrote:
=> No, it's just the root *filesystem*. fstat doesn't tell you the physical
=> path of the file.
=> : I know ls can tell me the inode corresponding to a pathname. Is there a
=> : command to do the reverse: to tell me the pathname corresponding to an
=> : inode number?
=> find ... -inum N
Okay, thanks. But, alas, when I do that find, it also never returns,
and hangs around forever in the "vnlock" state.
Can anyone suggest the problem of which this is indicative? Am I naive
in assuming that if there was a bad block, for example, eventually the
disk I/O would bomb out with EIO or similar?
"Without music to decorate it, time is just a bunch of boring production
deadlines or dates by which bills must be paid."
--- Frank Vincent Zappa