PROBLEM:        (QAR 46424)     (Patch ID: OSF375-350347)
********
This patch fixes a problem in which the UFS property list can become corrupted.

To reproduce this problem, complete the following steps:
1. Create a relatively large property value on a file.
2. Create another property value on the same file.
3. Change the property value created in Step 1 to a smaller value.
4. Run fsck with the -o flag.

The fsck command reports that the file system is corrupted and displays
the following error message:

        ** Phase 1 - Check Blocks and Sizes
        PROPERTY LIST BLOCK CORRUPTED I=3
        CLEAR? [yn]

PROBLEM:        (QAR 50363)     (Patch ID: OSF375-350357)
********
This patch fixes a problem with the fsck command. When fsck is run
on a non-existent file system or on a currently mounted file system,
it returns a success status of zero.  It should return a non-zero
status.

An example where this problem is exhibited is shown here:

# fsck /dev/rrz6c
/sbin/ufs_fsck /dev/rrz6c
** /dev/rrz6c
BAD SUPER BLOCK: MAGIC NUMBER WRONG
/dev/rrz6c: NOT LABELED AS A BSD FILE SYSTEM (swap)
# echo $?
0

ALSO:

# fsck /mnt
/sbin/ufs_fsck /mnt
Can't make sense out of name /mnt
# echo $?
0

PROBLEM:        (QAR 45510,QAR 52698)   (Patch ID: OSF375-117)
********
This patch fixes a problem with the ufs_fsck.  ufs_fsck would mishandle certain
dir corruptions, recursively asking the user if they want to fix it.

For example:
Corrupt the filesystem using fsdb.
#fsdb -w /dev/rz3g
>4:dir=45
>:q
#
Note: 4:dir=45 will change the inode number of the fourth directory entry to 45.

Run ufs_fsck with -o option.

#ufs_fsck -o /dev/rz3g
** /dev/rrz3g
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
DIRECTORY CORRUPTED  I=2  OWNER=root MODE=40755
SIZE=512 MTIME=Dec 10 11:21 1997
DIR=

SALVAGE? [yn] n

Directory corruption not fixed, cannot not handle multiple errors.

DIRECTORY SCAN CONTINUE? [yn]