Re: find bug?

[Bob Proulx]

Sam Halliday <address@hidden> [2002-12-12 21:01:35 +0000]:
> 
> i have recently been trying to write a simple script in order to verify
> a burnt CD, however i ran into this problem... GNU find seems to parse
> an iso9660 FS differently to others (at least ext3).

Find looks at filenames.  What does 'ls' say?  Find would be seeing
the same information.  If you (and 'ls') can't see the files then
'find' can't see the files either.

> i have tried passing all appropriate flags i know, such as -noleaf and i
> also tried -fstype iso9660, -fstype ext3 (i know what this flag really
> means... it was was just a shot in the dark it might do something..)

Pardon me but I don't think you ever mentioned anything that was
wrong.  I read your mail carefully but did not see where you said what
the problem was.  Those options you are mentioned seem very specific
to purposes that unless you need them you don't want to use them.

  http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
  http://www.tuxedo.org/~esr/faqs/smart-questions.html

I think you will find these references helpful.  Please read them and
then post a followup.

What is the problem?  Can you submit a small test case that would
allow someone to be able to recreate the error?  What command are you
running and how is it not doing what you think it should be doing?

> i feel slightly odd reporting this, since GNU find is such a well tested
> and respected tool... i would doubt my own use of it over any possible
> bug, but this time i have been left with no option.
> 
> is find parsing files as they appear on the hard-drive physically? can
> it therefore be forced to rather look at an arbitrary FS in a
> self-consist manner?

Yes and yes.  In unix everything is a file.  And as long as it is a
file it has a filename.  It does not matter if it is minix, ext2,
ext3, xfs, jfs, etc.

> thanks in advance, and many apologies if i have wasted your time...

Don't be discouraged.  It is a team effort and you are part of the
team.

Bob