SUMMARY/UPDATE: Where does ncheck get its inode list ?

From: eric@ee.pdx.edu
Date: Tue Feb 22 1994 - 04:08:58 CST

  My question was in regards to the discrepency between what UNIX reports
in the filesystem and what ncheck reports. A file created on a filesystem
often did not show up for hours in the list generated by ncheck (running
by hand, btw).

  I was, at the time, specifying the block device rather than the raw
device name to ncheck (the manpage said "filesystem" so I assume block).
Turns out that if I use the raw device instead, the entry will appear
immediately while still nothing from the block device :

        # df .
        Filesystem kbytes used avail capacity Mounted on
        /dev/sd1a 46343 35 41674 0% /tmp

        # touch zort
        # sync
        # ls -li zort
             4 -rw-r--r-- 1 root 0 Feb 21 17:58 zort

        # ncheck /dev/rsd1a
        /dev/rsd1a:
        20480 /screens/.
        3 /lockcenterline
        4 /zort
        18 /gsrv11105
        30 /hc25707
        32 /lost+found/.
        5120 /screens/S-eros/12055.ttyp3.ursula
        5122 /screens/S-eros/.

        # ncheck /dev/sd1a
        /dev/sd1a:
        20480 /screens/.
        3 /lockcenterline
        18 /gsrv11105
        30 /hc25707
        32 /lost+found/.
        5120 /screens/S-eros/12055.ttyp3.ursula
        5122 /screens/S-eros/.

  this condition will continue for several hours. Once it appears in the
block device, one can delete the file and the reverse will occur.

  Anyway, my immediate problem is solved using the raw device (which is
faster anyway), but I'm still curious to the above.

-eric 

--
  Eric Berggren             | "Parts of this product may be derived from
  Portland State University |  from UNIX and Berkeley 4.3 BSD systems..."
  eric@ee.pdx.edu           |                  -- Label on Solaris 2.x disk

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:55 CDT