[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::advfs_support

Title:AdvFS Support/Info/Questions Notefile
Notice:note 187 is Freq Asked Questions;note 7 is support policy
Moderator:DECWET::DADDAMIO
Created:Wed Jun 02 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1077
Total number of notes:4417

1057.0. "vchkdir reports //proc is corrupted ?" by ZPORDS::SONGHUAT () Fri May 09 1997 08:58

    Hi,
    
    On one of the V3.2d1 system when run the vchkdir on the root file
    system, it always reports the /proc is corrupted and with some lost
    files, 
    
    warning, encountered a fileset mounted on <//usr>
    vchkdir: warning, encountered a fileset mounted on <//data>
        1100Error in dirRec on page 0; //proc is corrupted
    
    Found possible lost file: ino/tag = 650
    Found possible lost file: ino/tag = 980
    Found possible lost file: ino/tag = 988
    
    I had tried to repair and delete the lost files and delete/recreate the
    /proc, but the error is still there.
    
    I had also tried to mkfdmn on the / again and did a vrestore from the
    previous backup, but the same error will always be there.
    
    Anyway to clean up both the / and /proc files system ?
    
    
    
T.RTitleUserPersonal
Name
DateLines
1057.1DECWET::MARTINFri May 09 1997 14:1351
In Digital UNIX, the /proc filesystem is a virtual file system that has
information on all the currently running processes.  It has nothing to do with
AdvFS, except that apparently in v3.2x, vchkdir doesn't handle it properly.

Your /proc is fine, it's vchkdir that's erroneously reporting errors about it.

I don't have a v3.2x system handy to test on, but on my v4.0 system I get:

# ./vchkdir /
path     : /
dev/fset : root_domain#root
type     : advfs
advfs id : 0x319a3a8f.000a0200.1

Scanning directories and files ...
vchkdir: warning, encountered a fileset mounted on <//tmp>
vchkdir: mount points will appear as lost files
vchkdir: warning, encountered a fileset mounted on <//usr>
vchkdir: mount points will appear as lost files
vchkdir: warning, encountered a fileset mounted on <//proc>
vchkdir: mount points will appear as lost files

...

Scanning tags ...
    1500
Searching for lost files ...

Found possible lost file: ino/tag = 7
Creating //lost+found
     100
Found possible lost file: ino/tag = 113
     300
Found possible lost file: ino/tag = 320
    1200
Found possible lost file: ino/tag = 1283

...

Found possible lost file: ino/tag = 1468
    1500
Found possible lost file: ino/tag = 2040

#

Apparently the warning about mountpoints looking like lost files wasn't in the
v3.2x version of vchkdir.  At a first glance I would say that your root
filesystem is just fine.  If you want me to investigate vchkdir some more, let
me know and I will.

--Ken
1057.2thanks !ZPORDS::SONGHUATMon May 12 1997 01:5213
    
    .1 Thanks for posting your test result and it does shows extra warning
    messages on the mount points which I don't see in .0. 
    
    I was worried because the /usr was corrupted before and I rely on
    utilites like vchkdir to verify the consistancy of all file systems.
    
    Just wonder why your version of vchkdir is different from mine. To my
    understanding, the V4.0 kit does not content those utilities under
    /usr/field directory.
       
    Regards,
    Song-Huat
1057.3KITCHE::schottEric R. Schott USG Product ManagementMon May 12 1997 04:344
Hi

In V4.0, these are in /sbin/advfs