Hi,
Recently I noticed a strange filesystem entry on one of our advfs filesets,
the entry looks like the following:
onyx:/some_directory # ls -la
total 214
drwxrwxrwt 4 root httpd 8192 Apr 26 01:46
drwxrwxrwt 4 root httpd 8192 Apr 26 01:46 .
drwxrwx--x3195 root system 188416 Apr 26 02:14 ..
---------- 1 root system 0 Apr 14 14:24 .the-zone
...
The entry I think of is the very first one, which is kind of a null-entry.
It seems to be linked to the current directory ('.') as any changes to that
affects the null-entries' info.
Just to make it clear, it is not a directory named ' ', it is '' and not
accessible at all in any way.
I supposed the reason was some fs inconsistency, in fact I ran verify on
that particular domain. After the files/directories check verify segfaulted
when trying to scan files/directories!
Has anyone every experienced such null-entries with advfs resp. a
segfaulting verify before?
Some weeks ago I pached tru64 5.0 with the latest patchkit available. I am
not sure whether that caused this inconsistency as I cannot assure the fs
was clean before.
I thought using advfs with tru64 5.0 would be a save thing, however it seems
that even with the latest patches advfs can cause huge problems. Hopefully
5.0a will fix some advfs related problems (will 5.0a actually include advfs
updates?).
Does anybody have any suggestions on what I could try in order to repair
that fileset resp. delete that particular entry?
Thanks in advance for any hints!
cheers,
Horst G Reiterer
Received on Wed Apr 26 2000 - 01:26:41 NZST