PROBLEM:	(ZPOB82799)	(Patch ID: OSF410-031)
********
This fixes a problem where a hang occurs on an AdvFS filesystem. 

This problem occurs when a thread is looping in routine "cleanup_closed_list".

Sample stack after forced crash:
	stop_secondary_cpu()
	panic("cpu_ip_intr: panic request")
	cpu_ip_intr()
	_XentInt()
	cleanup_closed_list()
	fs_cleanup_thread()

PROBLEM:        (GOZ100505)     (Patch ID: OSF410-400105)
********
A system will panic with the panic string "simple_lock: time limit
exceeded".
The stack trace of the panicing process is as follows:

        panic("simple_lock: time limit exceeded")
        simple_lock_fault()
        simple_lock_time_violation()
        msfs_getpage()
        u_seg_fault()
        u_map_fault()
        vm_fault()
        trap()
        _XentMM()

PROBLEM:        (QAR 50227)     (Patch ID: OSF410-400148)
********
This patch fixes an "ADVFS EXCEPTION" panic after an "advfs I/O error" message 
to the console.  The traceback of the panic thread will be as follows:

        panic()
        advfs_sad()
        ftx_fail_2()
        ftx_fail()
        fs_write()
        msfs_write()
        vn_write()
        rwuio()
        write()
        syscall()
        _Xsyscall().

PROBLEM:  	(HPAQ92E5E)	 (Patch ID: OSF410-400125)
********
The system is hung while running vdump and there is a thread with the followijg
signature (note: this is _NOT_ the vdump thread):

  0 imm_get_next_xtnt_desc() [../../../../src/kernel/msfs/bs/bs_inmem_map.c]
  1 imm_merge_xtnt_map()     [../../../../src/kernel/msfs/bs/bs_inmem_map.c]

PROBLEM:  	(HPXQ42587, QAR46237) (Patch ID: OSF410-400176)
********
On an AdvFS system, a broadcast message will cause the idle time to be reset to
zero.

			 (Patch ID: OSF400-176-1)
PROBLEM:  (QAR 36779)	 (Patch ID: OSF410-405054 reference information) 
********
This patch fixes a problem that occurs when running the NetWorker
Version 4.2c application.  The NetWorker application is unable to
reset the atime (access time) attribute on files being accessed. No
errors or warnings are displayed.

Without this patch, NetWorker Version 4.2c will not perform well.

PROBLEM:  (TKTR71564 QAR 36411) (Patch ID: OSF410-400217)
********
Systems running with AdvFS and LSM under heavy I/O loads can have sluggish
interactive performance.  In a DECsafe environment, these systems can 
encounter unexpected relocation of services.

PROBLEM:  (HPXQ43C4D, TKTR52185, QAR 46016) (Patch ID: OSF410-400217)
********
A system can hang after the message "syncing disks..." prints during a panic.
When a hang occurs, the "syncing disks..." message does not print entirely 
and the system does not take a dump.

A time-out mechanism was added to the "syncing disks" logic. This mechanism
improves the reliability of getting a dump by using the system clock to break
out of the "syncing disks" path and take a dump if no progress is being made
on reducing the number of buffers to be flushed. The numbers printed 
periodically between the "syncing disks..." and "done" messages are the number
of buffers left to flush.

PROBLEM:  (MGO102584)	 (Patch ID: OSF410-400228)
********
This patch fixes AdvFS to prevent the following two panics:

        AdvFS Exception  Module = 1, line = 1891

        kernel memory fault with the following stack trace:

_XentMM()
bs_refpg_int()
bs_refpg()
tagdir_get_info()
bs_bfdmn_activate()
bs_bfdmn_tbl_activate()
fs_fset_get_info()
msfs_real_syscall()
msfs_syscall()
syscall()
_Xsyscall()

PROBLEM:  (QAR 45580)            (Patch ID: OSF410-400239B)
********
Multithreaded applications that call the pthread_mutex_destroy routine
may fail when there are no threads referencing the mutex.  This is
caused by a race condition inside the pthread_mutex_unlock code.
The typical symptom will be a return value of EBUSY from pthread_mutex_destroy.

Due to the pthreads fix vdump and vrestore need to be redistributed.

PROBLEM:  (QAR 51304, QAR 51596) (Patch ID: OSF410-400231-1)
********
This patch fixes two problems that occur on AdvFS systems:

An AdvFS data corruption problem can occur in user files. This problem occurs
when AdvFS stores two different versions of a particular page (an 8K segment).
This problem will not produce either a core file or a return non-zero system
codes when accessing the corrupted file.  The verify command will not detect
the corrupted file.

This patch provides the following:
1. The OS is corrected to prevent any new files from being corrupted.
2. The verify program now recognizes data corruptions.
3. The verify -f command detects the corruption and moves the file into a
   temporary file. Another temporary file is created to show the contents
   of the corresponding "visible" page. These files are then available for
   analysis by the user for the purpose of manually repairing the corruption.
 
The following is an example of a recovery procedure.

To detect a corrupted file:

   Run the verify utility, which resides in /sbin/advfs.

   # verify test_domain
   +++ Domain verification +++

   Domain Id 32d3e638.000a46a0
   Checking disks ...

   Checking storage allocated on disk /dev/rz1a

   Checking mcell list ...

   Checking mcell position field ...

   Checking tag directories ...

   +++ Fileset verification +++

   +++ Fileset test_fileset +++

   Checking frag file headers ...

   Checking frag file type lists ...

   Scanning directories and files ...
   Overlapping frag data corruption detected in:
   File: <mount point>/50226.file.4
   Page: 1
   Run verify -f on this domain to enable recovery of this data.

   Scanning tags ...

   Searching for lost files ...

   #

The verify utility has detected a corrupted file in fileset test_fileset.  The
name of the file is "50226.file.4" and it is located in the highest directory
of the fileset when it is mounted.  The page that is corrupted is page 1.  
Verify also suggests running verify again using the -f flag to enable recovery
of the hidden data for page 1.

At this point there are two choices:

   1. Delete the file and recreate it. The corruption problem has been fixed
      on the system. The newly created file will not exhibit the undesired
      behavior.

   2. Run verify with the -f flag to identify the corrupted data.

   To identify the corrupted data:

   Run the verify command with the -f flag.

   # verify -f test_domain
   +++ Domain verification +++

   Domain Id 32d3e638.000a46a0

   Checking disks ...

   Checking storage allocated on disk /dev/rz1a

   Checking mcell list ...
   Checking mcell position field ...

   Checking tag directories ...

   +++ Fileset verification +++

   +++ Fileset test_fileset +++

   Checking frag file headers ...

   Checking frag file type lists ...

   Scanning directories and files ...
   Overlapping frag data corruption detected in:
   File: <mount point>/50226.file.4
   Page: 1
   Temporary files created representing the two versions of page 1 of file
   <mount point>/50226.file.4 
   Refer to the README file accompanying the patch for a description of how
   to use these temporary files to recover from this overlapping frag 
   corruption problem.  Scanning tags ...

   Searching for lost files ...

   #

The verify utility reports that it has created two temporary files in the
same directory as the corrupted file.  Mount the fileset to indentify these
two files:

   # mount test_domain#test_fileset /test
   # ls -l /test
   total 169
   drwx------   2 root  system      8192 Jan  8 13:23 .tags
   -rw-r--r--   1 root  system     24576 Jan  9 12:27 50226.file.1
   -rw-r--r--   1 root  system     40960 Jan  9 12:27 50226.file.2
   -rw-r--r--   1 root  system     32768 Jan  9 12:27 50226.file.3
   -rw-r--r--   1 root  system     24576 Jan  9 12:27 50226.file.4
   -rw-------   1 root  system      8192 Jan 13 14:32 50226.file.4.page_1.ext
   -rw-------   1 root  system      8192 Jan 13 14:32 50226.file.4.page_1.frag
   -rw-r-----   1 root  operator    8192 Jan  8 13:23 quota.group
   -rw-r-----   1 root  operator    8192 Jan  8 13:23 quota.user

The .ext and .frag files contain information from the corrupted area. In the
example above:

   50226.file.4              The original corrupted file
   50226.file.4.page_1.ext   A file containing the hidden version of page 1
                             of the corrupted file. A read() cannot
                             retrieve this data.
   50226.file.4.page_1.frag  A file containing the frag version of page 1
                             of the corrupted file.  This is the same data
                             that a read() of page 1 would return.

   To fix the corrupted file:

A
   1. View the .ext and .frag files to determine which to keep. Note that what
      might really be desired is a merge of the two.

      If the file 50226.file.4.page_1.ext contains the desired data, enter:

      # ln -s 50226.file.4.page_1.ext desired_page_1

      If the file 50226.file.4.page_1.frag contains the desired data, enter:

      # ln -s 50226.file.4.page_1.frag desired_page_1

      If a merge of the two must be done, do the merge and put the result
      into a new file called desired_page_1.

   2. Create a new fixed version of the corrupted file using the corrupted file
      and new file (desired_page_1 in this example).

      A. Copy page 0 (good page) from the corrupted file into a new file:

         # dd if=50226.file.4 of=newfile bs=8192 count=1

      B. Append the desired page 1 to the new file by seeking over 1 page in 
         the output file before writing:

         # dd if=desired_page_1 of=newfile bs=8192 count=1 seek=1

      C. Append the remainder of the original file to the end of the new file
         by skipping past the first two pages of the input file before reading,
         and seeking past the first 2 pages (already rewritten) in the output
         file before writing:

         # dd if=50226.file.4 of=newfile bs=8192 seek=2 skip=2

         Run the diff command on the new and the original file to confirm that
         only page 1 has changed to and that the difference is what is desired.
         For example:

         diff newfile 50226.file.4

      D. Rename the new file and remove the temporary files:

         # mv newfile 50226.file.4
         # rm 50226.file.4.page_1.ext 50226.file.4.page_1.frag desired_page_1

         If desired, the verify command can now be run on the domain again to
         confirm that the data corruption problem is gone.


FILE(s):

/sys/BINARY/advfs.mod				subset OSFADVFSBIN410
CHECKSUM: 27647   1131
/sbin/advfs/logread             		subset OSFADVFS410
CHECKSUM: 28446     32     RCSfile: logread.c     RCS: 1.1.2.3
/sbin/advfs/verify              		subset OSFADVFS410
CHECKSUM: 00307    224     RCSfile: verify.c      RCS: 1.1.15.2
/usr/lib/nls/msg/en_US.ISO8859-1/verify.cat	subset OSFADVFS410
CHECKSUM: 53996     12
/sbin/vdump					subset OSFADVFS410
CHECKSUM: 30119    432
/sbin/vrestore					subset OSFADVFS410
CHECKSUM: 36356    464
