Using 'find' across rmounted directories

JimG jim at bilpin.UUCP
Sun Feb 4 05:32:56 AEST 1990


    #{v_unix.5}
    THE PROBLEM:
Original disk configuration (gave no problems with find):
  hd0: /
  hd1: /usr
New disk configuration (gives problems with find from / or /usr):
  hd0: /
  hd1: /usr/acct 
       with /database/acct rmounted under  /usr/acct/RMOUNTS/DatabaseAcct
       with /usr/database  rmounted under  /usr/acct/RMOUNTS/UsrDatabase
       with /usr/spool     rmounted under  /usr/acct/RMOUNTS/UsrSpool
(Thus empty directories /database/acct, /usr/database, /usr/spool exist
on the 1st disk so that the rmounts to the real directories under
/usr/acct/RMOUNTS on the 2nd disk will work.)

Running find from / or /usr gives 'bad status' on :

  /usr/acct/RMOUNTS/UsrDatabase
  /usr/acct/RMOUNTS/UsrSpool
  /usr/acct/(various)
  /usr/include
  /usr/mail
  /usr/news
  /usr/preserve
  /usr/pub
  /usr/spool
  /usr/ucb
  /usr/dict
  /usr/catman
  /usr/man
  /usr/games

but *not* on :

  /usr/acct/RMOUNTS/DatabaseAcct	**
  /usr/acct/lost+found			**
  /usr/adm				**
  /usr/bin				**
  /usr/lib				**
  /usr/tmp

Listing the full output from 
  find /usr -print
shows that the files within the directories marked ** in the previous
group are listed correctly, but those listed for /usr/tmp are in fact
those in /tmp.

Further, files actually located under /database (on the 1st disk) are
listed as being under /usr/database (which exists, but is empty), and
those actually located under /usr/acct/RMOUNTS/DatabaseAcct are
additionally listed as being under /usr/database/acct (which doesn't
exist).

As an extra complication, if one searches from / for a filename which is
physically located *only* under /usr/acct/RMOUNTS/DatabaseAcct/dirname,
find lists it as occurring *three* times, under:
  /database/acct/dirname
  /usr/database/acct/dirname
  /usr/acct/RMOUNTS/DatabaseAcct/dirname

Now, I know there must be a logical pattern to all of this, but I'll be
damned if I can find it. Can anyone shed any light on this situation,
and suggest a solution? A good starting point would be an explanation of
what a find 'bad status' really means - what's it found (or, more
probably, not found) that it can't cope with?
-- 
    Another Fine Product from <mcvax!ukc!icdoc!bilpin!jim> <jim at bilpin.uucp>
			   {JimG : Hatfield, England}
 "Life is sure funny, isn't it, Chuck?" . . . . "It depends on the punch line."



More information about the Comp.unix.questions mailing list