SGI Logo
 
 

Patch 3289 : XFS rollup #14 for 6.2 : [IRIX 6.2]
INDEX

  • Relations
  • Release Notes
  • Inst Subsystem Requirements
  • Inst Subsystem Checksums
  • Inst Subsystem File Listings
  • Download Patch


    RELATIONS

    This patch replaces the following patches:
    1208, 1278, 1396, 1467, 1566, 1589, 1667, 1768, 1907, 2284, 2558, 2927, 2968, 3038

    This patch is incompatible with the following patches:
    1756, 1915, 2116, 2139, 2226, 2562, 2748

    This patch fixes the following bugs:
    254345 - xfsdump/xfsrestore needs operator notification feature
    261537 - stupid list traversal algorithm in xfs_sync
    282157 - XFS should allow punching holes in files
    303417 - XFS unmount is too slow
    311076 - PANIC: kern_malloc: invalid size -- 0 ( called by xfs_iread_extents)
    313079 - Customer wants quotas on xfs
    314110 - bug: mkfs with no options doesn't work on syquest drives (/fds*)
    315748 - xfsdump: would be nice to have total dump size printed when done.
    320290 - xfsdump with non-variable breaks device
    327721 - xfs_copy/xfs_restore should have an option for preserving original
                    UUID

    328307 - quota cannot be set up on XFS filesystems
    331296 - xfsdump to know 'mt unload'
    353197 - xfsdump inventory file records in progress dumps as not interrupted
    357358 - hang in xfs code running stress on big shiva system
    358502 - XFS needs a repair program
    362841 - xfs_bmap bites the dust at boot time
    364404 - xfsrestore will not correctly restore a sparse file with a hole at
                    the en

    364450 - xfsrestore can leave garbage in holes when restoring sparse files
    365043 - unique id's not sufficiently unique for XFS and XLV
    370704 - xfs 6.2 rollups (1208,1278) won't install on pacecar release
    372806 - IO_RSYNC code in xfs_read is broken
    378010 - write() succeeds to a block read-only device
    383270 - xfs_logprint corrupts xfs filesystem and/or log
    383959 - Assertion failure in attribute code
    385292 - xfs inode lookups are slower than they should be
    385316 - xfs superblock versioning doesn't allow easy upgrades/downgrades
    385376 - xfsdump prints trash message when by-inum open fails
    386036 - Another way for XFS to choke on corrupt inodes
    390257 - XFS does not update inode ctime for mv command
    391760 - VERY sparse file creation can cause XFS corruption
    392903 - MH R5000 with TOT DEBUG unix from 6/20 crashed while running sio
    393618 - malloc heap corruption in xfsdump
    394225 - xfsrestore 2.0 from miniroot doesn't print out progress message
    396248 - bmapi with long running transactions can return ENOSPC
    398935 - SHAREII disk quotas doesn't work with XFS
    402614 - xfsrestore incremental restores broken
    406537 - quota on root fs can hang mount
    406540 - quotaoff can lead to a crash
    407732 - quotaon on rootfs is inconsistent wrt limit-enforcement
    408639 - edquota -i complains when hardlimit=0, but softlimit > 0
    413256 - xfs_logprint doesn't like quota log records
    414414 - quotas on root filesystems is broken
    414919 - Mmap/ag stress test fails during heavy paging
    419313 - xfsdump not recycling tapes ?
    419563 - patch 1278 doesn't install quota.h
    419754 - patch 1278 doesnt like RT filesystems
    420023 - Increase XLV_MAXVOLS&gt10 in miniroot
    426893 - installing patch1467 breaks clogin and other desktop tools
    427424 - xfs_repair can generate a spurious error message
    428476 - xfsdump core dumps if local DAT tape starts with eof marker on IRIX
                    6.

    428626 - allocator bug in xfs_alloc_ag_vextent_near()
    433752 - Quota doesn't work over autofs filesystems
    435626 - xfs_restore "-i" should be able to read from stdin
    437401 - xfs_repair flaked out big-time on yantzi
    437495 - patch 1566 causes xfsdump to dump core on R5k Indy
    438657 - xfsdump 2.0 cannot determine block size on brand new tapes
    439096 - allocator bug in xfs_alloc_ag_vextent_size()
    439128 - kernel and utilities break on large inode numbers
    440334 - bad logging in symlink creation can cause crashes/corruptions
    440477 - symlink data shows up in wrong places in XFS filesystems
    442075 - bonsai-oct28e.NR-getting xfs read error
    443561 - xfs_repair seems somewhat broken on external log filesystems
    444272 - AIM3 hangs in xfs code
    445983 - 6.2 xfsdump remote dump fails to Sun tape drive
    446511 - need to make xfs do truly read-only mounts
    447743 - truncate() on xfs doesn't check write permissions
    451379 - XFS quotas can modify read-only filesystems
    451892 - xfs_repair doesn't completely work on attributes
    453046 - xfs_copy is broken
    453106 - xfs_repair -f doesn't work
    458528 - xfs_repair doesn't work on growfs'ed filesystems
    459447 - DFS is dependent on XFS patch releases
    459555 - DMAPI DM_EVENT_TRUNCATE event is not sent on open(O_CREAT|O_TRUNC)
    459567 - DMAPI does not generate events for memory mapped files
    460195 - BUG -- xfsdump will not work on Exabyte 8200 drive
    460982 - kernel Panic-tlbmiss:invalid kptbl entry when mounting external drive
    461457 - BUG -- xfsdump complains about uninitialized or incompletely initialized
                    tape

    462371 - attr_get overwrites kernel and user memory
    463620 - xfsdump from an origin2000 to a remote 5.3 tape drive fails
    464859 - xfs_repair can make bogus freespace btrees
    470689 - xfsdump fails with I/O error from 6.2 to 6.4
    470701 - xfsrestore inventory filter options need enhancement
    470817 - mkfs_xfs can build unusable xfs with certain block size
    473713 - '-p ###' status updates do not appear when xfsdump is to stdout
    474195 - requota gets confused with automaps installed
    474775 - superblock versioning change for backward compatibility
    477131 - seekdir() bug with xfs, getdents function
    477913 - xfsdump needs "overwrite" option
    479354 - edquota -i uses input as 1024byte blocks...but it is in BB
    480655 - Corruption in kernel heap.
    481782 - can not determine current directory from Solaris to IRIX DFS server
    492417 - XFS attribute log reservations are bogus
    494004 - An xfs_repair message has the arguments reversed
    494069 - xfs_repair can pop an assert in -n mode
    496799 - files get truncated when system crashes
    500173 - xfsdump on lofs filesystems is broken
    502702 - unclean unmounts and quota subsys removal don't mix
    502802 - NFS/XFS inode reference cache needs work
    503935 - attr_get, attr_remove, attr_list can fail to recognize empty attribute
                    for

    504513 - machine crashes with invalid inode number
    504578 - i/o jobs hang O2000 system
    511011 - Attributes on real-time files busted
    511889 - attr_get(2) buffer overwrite and system panic
    512294 - parallel realtime xfs allocations yield fragmentation
    513540 - XFS needs to be more careful when reading in inodes
    513865 - xfsdump needs option to generate a single media file
    513874 - xfsrestore does not restore mode of symbolic links
    514488 - fcntl(F_GETBMAP) gives unusual length for hole at end of file
    514540 - really large xfs rt allocations mangle filesystem
    516715 - full XFS filesystems can end up with inconsistent inodes
    519310 - aug17.NR large directory coredump and XFS corruption
    519614 - DMAPI code hangs machine in mutex_spinlock
    521368 - attr blk reservation isn't right
    523923 - xfs_repair needs to get 6.5 aware
    523961 - Unmount of a DMAPI file system can panic IRIx
    524254 - tokyo paniced while tring to unmount sick filesystem
    525377 - AIM7 processes hang waiting forever for logtick
    528130 - boot race condition with /tmp breaks flexlm server
    528257 - xfs returns ENOSPC when df reports there are free inodes
    534613 - Xfsrestore from minrmt misshandling forwarding media files.
    536065 - xfsdump progress reports failing when dumping to stdout
    539380 - xfs_repair doesn't work with non-h/w graph compatible disks
    539913 - xfs_repair dumps core
    540436 - mkfs_xfs can leave garbage at the end of the secondary superblocks
    540604 - mkfs_xfs -f and mkfs_xfs -p are xfs_repair unfriendly
    541304 - xfs_db -r opens filesystems in read/write mode
    545068 - xfs_repair needs to deal with non-zeroed secondary superblocks
    545119 - transposed values in an xfs_repair message
    545711 - xfsrestore merges extended file attributes.
    545725 - fcntl F_GETBMAP is misleading for a DMAPI file.
    546301 - xfsrestore -r aborts after a bad read
    549116 - Spurious DMAPI events generated by xfsrestore.
    549786 - xfs_repair loses realtime extents
    550476 - XFS superblock has a hole in it
    551378 - xfs_getattr() returns wrong preferred io size for realtime files
    551636 - NMI of hung filesystem and processes
    552459 - rm command panics system
    554467 - hang in xlog_state_sync()
    555963 - XFS synchronous I/O performs extremely poorly
    556399 - xfs_check doesn't check free inodes
    558181 - losing data on O2 during write
    559726 - xfsdump redundantly backs up DMF data
    559735 - xfsrestore can corrupt DMAPI files split across media.
    561238 - fcntl(fd, F_UNRESVSP) doesn't work for realtime files
    564234 - xfsdump 'mnt'/'fsid' inventory search stops after 1st found
    565130 - PANIC in xfs_bulkstat_one
    566872 - xfsrestore man page and Insight don't cod -F switch
    568618 - The DM_EVENT_NOSPACE event is delivered in an incorrect structure
                    forma

    568697 - xfs_repair will sometimes unnecessarily clear the root inode
    570775 - dm_getall_disp doesn't work if more than one DMAPI filesys exists
    571441 - Mandatory File Locking with XFS extremely slow
    571728 - bonnie crashed in killpg
    572246 - xfs_repair can blow away consistent attributes forks
    572249 - xfs_repair -n will die on full filesystems
    576029 - DMAPI dm_pending bug causes vnode freelist corruption
    576064 - A DMAPI DM_EVENT_DESTROY event can deadlock a CPU
    577158 - pre-6.5 xfs_repair's needs to disallow 6.5 filesystems with new features
                    

    577633 - xfs_repair not reading in large symlinks properly
    577808 - Load average calculation can be way way off
    578064 - ACL not preserved by xfsdump/xfsrestore
    580173 - truncate call in xfs_remove causes DMF to report file corruption
    580244 - xfsrestore: WARNING: unable to set root extended attribute for
    585904 - XFS clears setuid bit for writes as root
    590130 - panic caused by xfs quotas
    591630 - xfs_repair corrupts filesystems with allocation groups > 1 GB
    594577 - xfs_repair fails on filesystems > 1 TB with patch 2970 installed
    602912 - create script to close security hole.
    614319 - xfs_repair coredumps with Unexpected inode type
    616663 - xfs seekdir/readdir/telldir can go into a loop n32/n64
    616721 - panic: XFS aborting dirty transaction in mkdir
    622220 - xfsdump hangs in directory creation
    626381 - xfsrestore -t removes files
    628353 - write of realtime file can corrupt file system
    631822 - xfs_repair attribute regression
    705217 - BUG_ID 705217 IRIX FCNTL(F_RESVSP) ALLOWS ANOTHER USER'S DELETED
                    FILES TO BE RE

    705546 - BUG_ID 705546 XFSRESTORE RETURNS: INV: OPEN FAILED ON /VAR/XFSDUMP/INVENTORY/
                    


    RELEASE NOTES

    1. Patch SG0003289 Release Note

           This release note describes patch SG0003289 to IRIX 6.2.
    
           Patch SG0003289 replaces patches SG0001208, SG0001278,
           SG0001396, SG0001467, SG0001566, SG0001589, SG0001667,
           SG0001768, SG0001907, SG0002284, SG0002558, SG0002927,
           SG0002968, and SG0003038.
    
    
    1.1 Supported Hardware Platforms
           This patch contains bug fixes for all platforms.
    
    
    1.2 Supported Software Platforms
           This patch contains bug fixes for IRIX 6.2 (version
           1232792137) and IRIX 6.2 with Indigo^2 Impact R10000
           (version 1233007732).  The software cannot be installed on
           other configurations.
    
    
    1.3 Notice of Patch Dependencies
           This patch must not be installed unless patch 1389 6.2
           kernel rollup (or one of its successors) is already
           installed on the system.  If patch 3289 is installed on a
           system without patch 1389 or one of its successors, then the
           kernel will fail to link.  The link failure will complain
           that the symbol dnlc_lookup_fast_flags cannot be resolved.
    
           Included in this patch is an implementation of quotas for
           XFS file systems.  If you intend to use quotas with your XFS
           file systems, then you must also install patch 1287 (or one
           of its successors).  Patch 1287 contains modifications to
           the mount(1M) utility used to enable quotas on XFS file
           systems.
    
           If you intend to use quotas on an XFS root file system, then
           you must also install patch 1397 (or one of its successors)
           in addition to patch 1287.  Patch 1397 includes a version of
           sash which properly recognizes XFS file systems containing
           quotas; without it your root filesystem will fail to mount
           and your system start up will fail.
    
    
    1.4 Enabling Quotas on XFS File Systems
           This section contains a brief description of how to set up
           quotas on a system with XFS file systems.  See the
           quotas(4), repquota(1M), quotaon(1M), and quota(1) man pages
           for more details.
    
    
              o Install the eoe.sw.quotas subsystem from your IRIX 6.2
                CD if you have not already done so.
    
              o Install patches 3289, 1287, 1389, and 1397 or their
                successors.
    
              o Add the quota option to the lines in the /etc/fstab
                file corresponding to the file systems on which you
                wish to enable quotas.
    
              o Reboot your system.  It will come up with quotas
                enabled on all the file systems you specified except
                for the root file system.
    
              o If you want to enable quotas on the root file system,
                issue the command quotaon / as root, sync and reboot.
                Quotas will be enabled on the root file system when the
                system comes back up.
    
    
    1.5 If An XFS Root Filesystem Had Quotas Turned On ...
           This patch contains a fix for bug #414414 of patch 1278
           which may in certain cases have made quota accounting on the
           root XFS filesystem inaccurate.  Therefore, if an XFS root
           filesystem that has patch 1278 installed had quotas turned
           on, it is necessary that quotas be turned off (see
           quotaoff(1M) man page) and turned on after installing this
           patch. Refer to the previous section Enabling Quotas on XFS
           File Systems for details of the procedure.
    
    
    1.6 Quotas and Backing out XFS Patches
           Due to changes in the XFS filesystem on-disk data structures
           required for quotas to operate, once quotas have been
           enabled on an XFS filesystem from that point on, only
           systems running XFS rollup patch 1278 or a successor will be
           able to mount the filesystem.  Machines running only IRIX
           6.2 or IRIX 6.2 with XFS rollup patches 1208 or 1396
           installed will not be able to mount a filesystem that has
           had quotas enabled even if the quotas are currently
           disabled.  The quota-related changes, once made, are
           permanent.  The only way to move a filesystem back to a
           pre-quota state is to xfsdump the filesystem, re-mkfs the
           filesystem, and xfsrestore.
    
           If quotas have never been enabled on an XFS filesystem, that
           filesystem will remain mountable by any IRIX 6.2 machine.
    
    
    
    1.7 DMAPI Implementation Changes
           Patch 3289 contains changes to the DMAPI interface.
           Numerous bugs have been fixed, and the current
           implementation of DMAPI is not compatible with previous
           versions of the interface (prior to patch 1907).
    
           The original DMAPI interface was intended for use in
           products being developed.  Changes were anticipated as
           applications developers gained experience and as the DMAPI
           specification evolved.  The original SGI implementation was
           based on version 2.1 of the specification.  The current
           implementation is based on the X/Open document Systems
           Management: Data Storage Managment (XDSM) API dated February
           1997.
    
           The current implementation follows the specification more
           closely than the previous implementation.  All required
           functions and structures mentioned in the specification are
           defined and prototyped in the header file &ltsys/dmi.h&gt.  Some
           optional components are defined but unimplemented so that an
           application will compile and link if the optional component
           is used.  For example, the optional function
           dm_symlink_by_handle() is prototyped in &ltsys/dmi.h>, but a
           call to dm_symlink_by_handle() returns ENOSYS.  The comments
           and prototypes in &ltsys/dmi.h> document differences between
           the SGI implementation and the DMAPI specification.
    
           The access rights mentioned in the specification are not
           implemented.  Specifically the DMAPI functions
           dm_request_right(), dm_release_right(), dm_query_right(),
           dm_upgrade_right() and dm_downgrade_right() do not work as
           described in the specification.  The connection between
           DMAPI access rights and the XFS filesystem locks is missing.
           However applications which do not need full rights support
           and which only make dm_xxx_right calls in order to satisfy
           the input requirements of other DMAPI calls should be able
           to use these routines to avoid having to implement special-
           case code for SGI platforms.  Applications which truly need
           the capabilities of a full implementation of rights will
           unfortunately have to come up with alternate software
           solutions until such time as rights can be completely
           implemented.
    
           If you are using the DMAPI interface in patch 3289, then the
           base Hierarchical Storage Management Support package must
           have been installed first.  When installing patch 3289,
           select both the Hierarchical Storage Management Support and
           the Development Execution Header subproducts.  If the
           eoe_sw.xfs filesystem component of patch 3289 is installed
           with the base release of eoe_sw.dmi, the resulting kernel
    
    
           will generate warning messages at kernel link time.  Also,
           the resulting kernel will not execute DMAPI functions
           correctly.
    
           Patch 3289 contains corrections for the DMAPI handling of
           memory mapped files.  However, with these corrections it is
           possible to hang a system if a file with DMAPI managed
           regions is being memory mapped and if the DMAPI application
           needs additional memory (for itself or for spawned
           processes) to process the managed region request.  The
           potential for this hang is corrected in kernel rollup patch
           2119 and its successors.
    
           Following are some specific differences between the current
           implementation and the previous DMAPI implementation.
    
              o The function prototypes and data structures now always
                match the specification, except as noted earlier.
    
              o The truncate was previously missing for a file which
                existed but was opened with O_CREAT|O_TRUNC.
    
              o The asynchronous events are now always sent even when
                an operation fails.  This applies to the postcreate,
                postremove, postrename, postlink, postsymlink,
                attribute, and destroy events.
    
              o The destroy event will return the attribute specified
                by the set_return_on_destroy() function.
    
              o The postcreate event was previously being sent even if
                the file was actually not created.
    
              o Previously the function dm_set_eventlist() allowed one
                to set the read, write, and truncate events directly on
                a file.  Now these events must be specified using the
                standard function dm_set_region().  Since multiple
                managed regions are not supported, the region specified
                for  dm_set_region() typically uses an offset of zero
                and a length of zero to specify the entire file.
    
              o Previously, memory mapped access to a file would not
                generate DMAPI events.  This has been changed so that a
                read or write event will occur at the time a file is
                mapped.  If the file is being mapped for execution
                (e.g., and exec type system call) the event is a read
                event for the entire file.  If the file is being mapped
                by the mmap() system call, a read or write or write
                event for the correct range is generated.  Before
                sending the final response for a write event, the DMAPI
                application must make sure that there are no longer any
    
    
                read or write managed regions on the file.  This is
                necessary because in the memory map case, it is not
                possible to reliably detect subsequent read or write
                events for the mapped file.  Similarly, before sending
                the final response for a read event, the DMAPI
                application must ensure that there no longer is a read
                managed region on the file; a write region is allowed.
    
              o The dm_assoc_handle(), dm_disassoc_handle(),
                dm_query_token(), and open_by_handle() functions
                functions have been removed.
    
    
    1.8 This Patch Contains a New Miniroot
           This patch contains a new miniroot with all the fixes listed
           below.  This was done primarily to supply a 6.2 miniroot
           with the correct xfs_repair and mkfs_xfs binaries in this
           patch, and secondarily in case some of the kernel bugs were
           encountered while running the earlier version of the
           miniroot.
    
           No filesystem format changes were introduced in this patch,
           so the earlier miniroots will be able to mount all
           filesystems created and modified under this patch.
    
    
    1.9 Bugs Fixed by Patch SG0003289
           This patch contains fixes for the following bugs in IRIX
           6.2.  Bug numbers from Silicon Graphics bug tracking system
           are included for reference.  For bugs fixed in prior
           patches, fix descriptions are grouped under the replaced
           patches.
    
              o Implement the xfs_chver command to allow admins to
                enable the unwritten extent feature. This closes a
                potential data security hole. (bug #602912)
    
              o Seekdir/telldir sequences could cause infinite loops in
                in-inode directories (bug #616663).
    
              o xfsrestore dumps core during directory creation on very
                large filesystems (bug #622220).
    
              o xfsrestore can remove files when used with the '-t'
                option (bug #626381).
    
              o Fix a realtime file problem that occurs with fix for
                bug #705217 installed (bug #628353).
    
              o xfs_repair was incorrectly reporting repairs for misc
                type inodes that had attribute blocks (bug 631822).
    
    
              o Allow tracking of unwritten extents on a file to
                prevent uninitialized data from being available to the
                user (bug #705217).
    
           Bugs fixed in patch SG0003038:
    
              o Add a new tunable, xfs_refcache_percent, in mtune/xfs
                that allows the size of the NFS/XFS inode reference
                cache to be set to a percentage of ncsize.  Large
                reference caches typically result in better allocation
                for NFS written files as well as lower system overhead.
                However, reference caches that are too large can result
                in too many filesystem blocks being temporarily
                allocated to an NFS written file for too long.  This
                can result in problems if users are near their quota
                limits as the overallocated blocks are counted against
                the quota limits.  Reducing the size of the reference
                cache will result in the blocks overallocated to NFS
                written files being freed in a more timely fashion
                making the quota information more accurate (bug
                #502802).
    
              o xfsrestore to rmt drive misshandling 'fsf' of media
                files (bug #534613).
    
              o Xfsdump progress reports failing when dumping to stdout
                (bug #536065).
    
              o Xfsrestore aborts after a bad read (bug #546301).
    
              o Stat's st_blksize field did not return the realtime
                extent size for realtime files (bug #551378).
    
              o DMAPI files restored with xfsrestore could be corrupted
                if DMF were active on the same file and the file
                spanned tapes (bug #559735).
    
              o Correct three problems with the Realtime filesystem.
                xfs_bmap(1M) of a realtime file now returns the actual
                realtime blocks allocated to the file.  Correct a data
                corruption problem when using fcntl(F_UNRESVSP) to a
                realtime file less than a filesystem block in length.
                This modification correctly punches the hole in the
                realtime partition of the filesystem. The final change
                correctly releases realtime extents when freeing space
                greater than the configured realtime allocation extent
                size. (bug #561238).
    
              o Dump inventory searches with xfsdump/xfsrestore based
                on a mount point would quit after finding the first
                match (bug #564234).
    
    
              o The SGI_FS_BULKSTAT system call did not verify the
                buffer pointer being passed in and would panic the
                system if NULL (bug #565130).
    
              o Xfsrestore not properly restoring extended attributes
                on directories (bug #578064).
    
              o Attempting to remove a DMF offline file can corrupt DMF
                file state in a full file system (bug #580173).
    
              o Running quotaoff or unmounting a filesystem with
                quotas, while kernel memory was low, could result in
                crashes or kernel hangs (bug #590130).
    
              o xfs_repair's handling of alternate superblocks was
                incorrect when the allocation group size was larger
                than the default 1GB.  This resulted in filesystem
                corruption when xfs_repair was run in such cases (bug
                #591630).
    
              o xfs_repair would fail to run successfully on
                filesystems larger than 1TB (bug #594577).
    
              o xfs_repair would abort with the message "Unexpected
                inode type" if the mode bits in the inode were
                corrupted in a certain pattern (bug #614319).
    
              o When seekdir is used to seek into the middle of a set
                of directory entries with the same hash value, the
                wrong entry is returned.  This can cause an infinite
                loop in such programs by repeating entries returned by
                readdir (bug #616663).
    
              o Adding an entry to a mostly full in-inode directory,
                where the filesystem blocksize is 512 bytes and the new
                entry name is long, could cause a panic "XFS aborting
                dirty transaction" (bug #616721).
    
           Bugs fixed in Patch SG0002968:
    
              o Xfs_repair didn't check the integrity of user mode
                attribute data (bug #451892).
    
              o Sometimes FlexLM was unable to perform tasks prior to
                S58rmtmpfiles.  This problem is corrected in
                S12filesystems (bug #528130).
    
              o Xfsrestore/xfsdump man pages and usage statements
                inconsistent (bug #566872).
    
    
              o In very rare cases, xfs_repair would clear the wrong
                inode when deleting an existing "lost+found" directory.
                Sometimes this resulted in the root inode being cleared
                (bug #568697).
    
              o Xfs_repair checked multiblock symbolic links for
                consistency incorrectly.  This case can only happen
                with 512-byte block filesystems and links longer than
                512 bytes (bug #577633).
    
              o Processes waiting for XFS log space were being counted
                as short-term waiters, causing the load average to read
                higher than it really should be (bug #577808).
    
              o xfsrestore extraneous warning message for xfs
                attributes (bug #580244).
    
              o Root writing to a setuid file will clear the setuid
                bit.  This was introduced by the fix to 571441 (bug
                #585904).
    
           Bugs fixed in Patch SG0002927:
    
              o In large-block filesystems, attribute operations would
                panic with "xfs_log_write: reservation ran out. Need to
                up reservation" (especially true on 64k block
                filesystems) (bug #492417).
    
              o Attribute set operations could either fail or cause
                filesystem corruption in full filesystems (bug
                #521368).
    
              o It was possible to get the panic "xfs_log_write:
                reservation ran out. Need to up reservation" especially
                on removals of complex files (with many extents) (bug
                #552459).
    
              o The DMAPI function dm_getall_disp() does not work when
                more than one filesystem has a disposition registered.
                (bug #570775)
    
              o Mandatory file locking for non-root users is very slow
                under XFS.  (bug #571441).
    
              o Kernel memory corruption can occur, leading to a
                variety of crashes, due to a bug in sync (bug #571728).
    
              o In certain cases, xfs_repair will unnecessarily destroy
                all XFS extended attribute attached to a file (bug
                #572246).
    
    
              o xfs_repair -n could fail on full filesystems (bug
                #572249).
    
              o DMAPI applications which used the dm_pending() function
                to allow NFS server daemons to process other files
                while a file recall was in progress could see system
                crashes due to a corrupt vnode freelist chain.  (bug
                #576029).
    
              o DMAPI applications which use the token provided with an
                event on subsequent dm_request_right() calls could
                encounter a CPU deadlock when dm_release_right() is
                eventually called if some other process unlinks the
                affected file during the period the DMAPI right is held
                (bug #576064).
    
              o New filesystem features have been introduced in 6.5-
                generated (mkfs'ed) filesystems that are not understood
                by 6.2 kernels.  If a xfs_repair is run against a
                filesystem with such features present, it will detect
                the feature and direct the user to run a 6.5 version of
                xfs_repair (bug #577158).
    
           Bugs fixed in Patch SG0002558:
    
              o It was possible for sync on busy filesystems to
                repeatedly fail to sync all inodes to disk (bug
                #261537).
    
              o Fsync and fdatasync calls to XFS filesystems (for
                regular files and block devices) would ignore errors
                and pass back success to the caller even if the
                operation failed (bug #378010).
    
              o It was possible for files to get truncated when the
                system crashes.  (bug #496799).
    
              o Mount of an XFS filesystem failed with an I/O error if
                the filesystem had not been shutdown cleanly and the
                quotas subsystem had been removed in the interim (bug
                #502702).
    
              o Xfs quotas can crash the system at filesystem unmount
                time.  (bug #524254).
    
              o It was possible for a filesystem with large amounts of
                metadata activity, especially removing files with many
                extents to deadlock on the logtick semaphore.  (bug
                #525377)
    
    
              o xfs returns ENOSPC when df reports there are free
                inodes (bug #528257).
    
              o xfs_repair's -f option would not work to allow repair
                of an in-file filesystem (bug #539380).
    
              o xfs_repair can dump core after printing "Assertion
                failed: bno_bt-&gtnum_free_blocks <= XFS_BTREE_MAXLEVELS"
                (bug #539913).
    
              o For sufficiently large filesystems, mkfs_xfs would not
                properly initialize all the secondary superblocks.
                This would confuse xfs_repair when repair was attempted
                on such a filesystem (bug #540436).
    
              o Filesystems created with mkfs_xfs -p and/or -f flags
                would confuse xfs_repair due to the absence of the
                realtime special inodes in this case.  Mkfs_xfs has
                been changed to always allocate these inodes in a way
                predictable by xfs_repair (bug #540604).
    
              o xfs_db -r was opening filesystem devices read/write
                instead of read-only (bug #541304).
    
              o Due to a mkfs bug (#540436), xfs_repair could be
                confused about the validity of secondary superblocks in
                some (large) filesystems and refuse to repair them (bug
                #545068).
    
              o Several xfs_repair error messages had bad or missing
                arguments, yielding wrong output or core dumps (bug
                #545119).
    
              o xfsrestore blindly adds extended attributes to files.
                This means attributes added after the dump but before
                the restore are not properly deleted upon the restore
                (bug #545711).
    
              o Changed fcntl(F_GETBMAP) to generate a DMAPI read event
                for files which have the DM_EVENT_READ bit set in a
                DMAPI (-o dmi) filesystem.  This will usually result in
                the DMAPI file that is offline being restored to disk
                before the fcntl(F_GETBMAP) is allowed to complete.
                This behavior does not occur if the file was opened by
                handle (FINVIS).  (bug #545725)
    
              o xfsrestore generates spurious DMAPI events in a -o dmi
                filesystem (bug #549116).
    
              o Xfs_repair would not account correctly for the extents
                in a realtime file except for the first extent.  Thus
    
    
                any such file would be removed by xfs_repair (bug
                #549786).
    
              o The XFS superblock had some uninitialized data in it
                that should not have been there (bug #550476).
    
              o Certain XFS operations can hang the system (bug
                #551636).
    
              o Process can hang in xlog_state_sync() waiting for the
                incore log to be flushed to disk (bug #554467).
    
              o The performance of O_DSYNC writes to XFS files was much
                less than it could have been (bug #555963).
    
              o xfs_check failed to complain about inconsistent data in
                free inodes (bug #556399).
    
              o fsync was not transactionally updating the inode size
                which meant that on a crash or power failure data from
                several previous file extending writes could be lost.
                (bug #558181).
    
              o xfsdump redundantly backs up data stored by the DMF
                (Data Migration Facility).  A -a option was added to
                xfsdump for use with DMF filesystems (bug #559726).
    
              o The DMAPI event DM_EVENT_NOSPACE was returned as a data
                event rather than as a namespace event (bug #568618).
    
           Bugs fixed in Patch SG0002284:
    
              o Unmounting an XFS filesystem could take much longer
                than necessary (bug #303417).
    
              o xfsdump inventory file records in progress dumps as not
                interrupted (bug #353197).
    
              o xfsrestore can leave garbage in holes when restoring
                sparse files (bug #364450).
    
              o If attr_get was called with a size smaller than the
                actual attribute size on a shortform attribute area
                (fits in the inode), kernel memory corruption and/or a
                crash could result (bugs #462371 and #511889).
    
              o xfsrestore inventory filter options need enhancement
                (bug #470701).
    
              o Filesystems larger than 1/2 terabyte would see panics
                ("Invalid inode number 0xffffffffnnnnnnnn") if there
    
    
                were inodes in the part of the filesystem from 1/2
                terabyte up to 1 terabyte (bug #504513).
    
              o On a I/O intensive system, a hang can occur between a
                process executing in the xfs write system call code and
                the xfsd daemon trying to push delayed write and
                delayed allocated data out to disk (bug #504578).
    
              o Adding user-mode attributes to realtime files would
                cause filesystem corruption (bug #511011).
    
              o Files created in the realtime area of a filesystem tend
                to be much more fragmented than those in the normal
                data area (bug #512294).
    
              o XFS performs more consistency checking when reading in
                inodes (bug #513540).
    
              o xfsdump needs option to generate a single media file
                (bug #513865).
    
              o xfsrestore does not restore mode of symbolic links (bug
                #513874).
    
              o fcntl(F_GETBMAP) would return an incorrect length value
                when the starting offset was nonzero and the last
                extent returned was a hole at the end of the file (bug
                #514488).
    
              o Realtime file allocations of at least 2^21 filesystem
                blocks (this is usually done with the F_RESVSP or
                F_ALLOCSP fcntl call) will cause a corrupted filesystem
                (bug #514540).
    
              o Extremely full XFS filesystems may end up with
                inconsistent inodes (bug #516715).
    
              o Removals of large directories can cause a kernel crash
                (bug #519310).
    
              o DMAPI usage can hang CPUs in mutex_spinlock (bug
                #519614).
    
              o This patch includes changes to make xfs_repair work
                against filesystems mkfs'ed by machines running IRIX
                6.5 (bug #523923).
    
              o The unmount of a DMAPI filesystem may possibly panic
                IRIX (bug #523961).
    
    
              o xfsrestore returns: inv: open failed.  The new
                xfsinvutil command used with the -C command line option
                fixes this (bug #705546).
    
           Bugs fixed in Patch SG0001907:
    
              o xfsdump/xfsrestore needs operator notification feature
                (bug #254345).
    
              o xfsdump now prints total size of non-dir files dumped
                when done (bug #315748).
    
              o xfsdump with non-variable breaks device (bug #320290).
    
              o xfsdump did not know about mt unload (bug #331296).
    
              o xfsdump/restore malloc heap corruption when
                stdout/stdin is the destination/source (bug #393618).
    
              o xfsrestore 2.0 from miniroot doesn't print out progress
                message.  Note that actual status update intervals may
                be longer than the specified (by the -p command line
                option) interval in this case (bug #394225).
    
              o xfsdump not recycling tapes.  The overwrite option
                fixes this problem (bug #419313).
    
              o xfsdump core dumps if local DAT tape starts with eof
                marker (bug #428476).
    
              o xfsrestore "-i" would not work if input was from stdin
                (bug #435626).
    
              o xfsdump 2.0 cannot determine block size on brand new
                tapes.  The overwrite option fixes this problem (bug
                #438657).
    
              o xfsdump remote dump fails to Sun tape drive (bug
                #445983).
    
              o DMAPI DM_EVENT_TRUNCATE event is not sent on
                open(O_CREAT|O_TRUNC) (bug #459555).
    
              o DMAPI does not generate events for memory mapped files
                (bug #459567).
    
              o xfsdump does not work on Exabyte 8200 drive (bug
                #460195).
    
              o xfsdump complained about uninitialized or incompletely
                initialized tapes (bug #461457).
    
    
              o xfsdump from an Origin 2000 to a remote 5.3 tape drive
                did not work (bug #463620).
    
              o xfsdump fails with I/O error from 6.2 to 6.4 (bug
                #470689)
    
              o Under certain extremely rare circumstances, mkfs will
                generate a XFS filesystem that will cause a panic when
                used (bug #470817).
    
              o -p ###' status updates do not appear when xfsdump is to
                stdout.  Note that actual status update intervals may
                be longer than the specified (by the -p command line
                option) interval in this case (bug #473713).
    
              o Some quota utilities like repquota and quot did not
                sometimes work properly when the target filesystem was
                lofs/autofs mounted (bug #474195).
    
              o This fix allows 6.2 kernels to mount filesystems that
                will be created by IRIX 6.5 (bug #474775).
    
              o For o32 applications, readdir (getdents) may skip some
                directory entries when seekdir is used, especially in
                large directories (bug #477131).
    
              o xfsdump needs "overwrite" option (rfe #477913).
    
              o edquota -i option did not interpret the limits read in
                from the input file in the correct units (bug #479354).
    
              o The mount system call without the dataptr argument
                could cause kernel memory corruptions and panics (bug
                #480655).
    
              o Readdir (getdents, ngetdents) calls returning 64-bit
                offsets were supposed to be unique offset values, and
                were not.  This could cause infinite loops when using
                seekdir/telldir (bug #481782).
    
              o An error message in xfs_repair had two values reversed
                (bug #494004).
    
              o xfs_repair -n could hit an assert "agip-&gtagi_seqno ==
                agno" and core dump (bug #494069).
    
              o xfsdump did not sometimes work properly when the target
                filesystem was lofs/autofs mounted.  The same was true
                for some operations in the grio subsystem (bug
                #500173).
    
    
              o attr_get, attr_remove, and attr_list would fail in some
                cases, returning EDIRCORRUPTED, when there were no
                attributes attached to the file in question (bug
                #503935).
    
           Bugs fixed in Patch SG0001768:
    
              o The miniroot in this patch can support up to 40 XLV
                volumes.  (bug #420023)
    
              o xfs_repair failed on filesystems that had been grown
                using growfs(1), complaining that the primary
                superblock had a bad magic number and not finding any
                secondary superblocks (bug #458528).
    
              o This patch adds an internal interface between XFS and
                SGI's DFS implementation making it possible to patch
                them independently (bug #459447).
    
              o It is possible to panic recovering an XFS filesystem if
                the kernel log buffer data area used in recovery is
                adjacent to unmapped kernel virtual memory (bug
                #460982).
    
              o xfs_repair can generate filesystems with incorrect
                freespace btrees (bug #464859).
    
           Bugs fixed in Patch SG0001667:
    
              o Running xfs_logprint on a live filesystem could result
                in filesystem corruption if the machine crashed
                immediately thereafter (bug #383270).
    
              o Deadlock was possible under heavy filesystem stress
                (multiple threads creating and deleting files, for
                instance) (bug #444272).
    
              o Read-only mounts of cleanly unmounted XFS filesystems
                would issue disk writes to the XFS log to zero parts of
                the log and write an unmount record and allow certain
                quota operations to occur.  With this patch, if an XFS
                filesystems that was cleanly unmounted is mounted
                read-only, no disk writes will be issued to the
                filesystem (bugs #446511 and #451379).
    
              o Truncate system calls to files in XFS filesystems did
                not check for write permission correctly.  A current
                kernel rollup patch is also required for the complete
                fix to this problem (bug #447743).
    
    
              o In certain rare cases, xfs_copy would not copy all the
                blocks in a filesystem.  The situation that triggers
                the bug is a little more likely on filesystems made by
                IRIX 6.3 and IRIX 6.4 kernels (bug #453046).
    
              o xfs_repair -f (repair a filesystem in a file) didn't
                work (bug #453106).
    
           Bugs fixed in Patch SG0001589:
    
              o Mkfs on a Syquest removable drive would print an error
                message about a write failure, but actually work
                correctly.  If a legitimate write error occurred during
                mkfs, it would be reported, but the mkfs would continue
                (bug #314110).
    
              o There was a bug in the attribute rename code which
                could cause a system panic (bug #383959).
    
              o The quota(1) utility did not report information on
                autofs filesystems (rfe #433752).
    
              o xfs_repair would fail on a number of extreme filesystem
                corruptions (bug #437401).
    
              o xfsdump would core dump on R4600 or R5000 platforms
                after installing patch 1566 (bug #437495).
    
              o Bug in the allocator code where we would use a
                previously allocated block which could result in a
                panic or corrupt the file system (bug #439096).
    
              o Some utilities did not handle very large (illegal)
                inode values properly which could lead to incorrect
                behavior if the filesystem becomes corrupted (bug
                #439128).
    
              o Symbolic link values whose length was greater than or
                equal to 512 bytes in a 512-byte block filesystem could
                cause memory corruption during filesystem recovery (bug
                #440334).
    
              o Symbolic links which did not fit in the inode, and were
                removed before a crash, could result in corruption with
                the symbolic link value reappearing in the block even
                though it was used for something else (bug #440477).
    
              o Multiple parallel opens of a single directory could
                race, resulting in failure of a subsequent getdents
                (readdir) call (bug #442075).
    
    
              o On filesystems with external logs, xfs_repair would
                think that some number of the first blocks in the
                filesystem were used by both the log and the filesystem
                and reclaim those blocks for the log, losing data in
                the filesystem and possibly damaging a consistent
                filesystem (bug #443561).
    
           Bugs fixed in Patch SG0001566:
    
              o Some programs accessing files via mmap(2) or using the
                user level semaphore facility (see usinit(2)) would
                core dump randomly after installing patch 1467 (bug
                #414919).
    
              o Bug #414919 would cause clogin and other desktop tools
                to fail on certain combinations of platforms and
                installed patches (bug #426893).
    
              o xfs_repair used to issue a spurious warning message
                about a directory entry referencing a free inode when
                run on a filesystem with a large root directory and an
                existing lost+found directory.  The message was
                spurious since the program itself clears the lost+found
                inode while running and then recreates it later.  So
                the warning message could mislead users into thinking
                that the filesystem was corrupt when it fact it was not
                (bug #427424).
    
              o On a full file system, it is possible to reallocate a
                filesystem data block that has already been allocated
                which could result in a panic or corrupt the file
                system (bug #428626).
    
           Bugs fixed in Patch SG0001467:
    
              o XFS did not have full support for punching holes in
                files (bug #282157).
    
              o A truncate system call on a fifo device special file
                could cause the system to panic (bug #311076).
    
              o This patch and its miniroot include a program and man
                page for a program named xfs_repair(1M) that repairs
                corrupted XFS filesystems (rfe #358502).
    
              o Previous XFS rollup patches would not install on IRIX
                6.2 for Indigo2 Impact R10000.  This patch and its
                successors will (bug #370704).
    
              o Corruption in certain fields in the on disk XFS inode
                structure could lead to a system crash (bug #386036).
    
    
              o Incremental restores using xfsrestore were broken.  It
                was not processing removes, links, and renames (bug
                #402614).
    
              o Disk quotas on XFS root filesystems was broken in patch
                1278; it was possible to get inaccurate quota
                accounting.  In extreme cases where a very large number
                of users owned files on the root filesystem, it was
                also possible for the system to hang when trying to
                turn quotas on.  It is necessary to turn quotas off and
                on again on the root filesystem for rectification (bugs
                #406537 and #414414).
    
              o A crash was possible in certain cases when turning off
                quotas on busy XFS filesystems (bug #406540).
    
              o Turning on quota limit enforcement on root XFS
                filesystems required a reboot in patch 1278. That was
                an unnecessary restriction (bug #407732).
    
              o Edquota(1M) option -i erroneously complained when a
                user's hardlimit was zero and the softlimit was greater
                than zero (bug #408639).
    
              o xfs_logprint(1M) did not recognize XFS quota log
                records; it would core dump as a result (bug #413256).
    
              o A previous XFS rollup patch (patch 1278) did not
                contain the latest version of the quota.h header file
                (bug #419563).
    
              o A panic was possible in a previous XFS rollup patch
                (patch 1278) on XFS realtime filesystems (bug #419754).
    
           Bugs fixed in Patch SG0001278:
    
              o XFS as originally released had no support for quotas
                (bugs #313079 and #328307).
    
              o Using the O_RSYNC open flag with files in XFS file
                systems would cause accesses of the file after the
                first read to hang (bug #372806).
    
              o Inode reads were slower than was necessary on small-
                block filesystems (bug #385292).
    
              o The quota and inode read changes required changing the
                version number in the XFS superblock.  The versioning
                scheme has been changed to be more flexible.  With this
                patch, if a boot filesystem is made to have the new
                superblock version number (for instance, by using
    
    
                quotas on it) then the sash patch (SG0001397 or its
                successor) and the mount patch (SG0001287 or its
                successor) are also necessary (bug #385316).
    
              o xfsdump printed a trash message when its open of a file
                failed (bug #385376).
    
              o When a file is renamed its inode change time is not
                updated (bug #390257).
    
              o Very sparse files, with blocks separated by more than
                2^32 blocks, can get corrupted when more block
                insertions are done (bug #391760).
    
              o A very full allocation group in a filesystem can have
                less than optimal blocks added to files when the file
                is extended (bug #392903).
    
              o A very full filesystem can cause deadlocks when
                directory or attribute blocks are added (bug #396248).
    
              o SHAREII disk quotas did not work on XFS filesystems
                (rfe #398935).
    
           Bugs fixed in Patch SG0001396:
    
              o A deadlock was possible in XFS under heavy stress (bug
                #357358).
    
           Bugs fixed in Patch SG0001208:
    
              o xfs_copy now has an additional option -d.  The -d
                option will make xfs_copy duplicate the filesystem ID
                (UUID).  xfs_copy typically generates a new filesystem
                ID for duplicated filesystems.  This allows the
                original and duplicated filesystems to be used
                simultaneously.  The -d option allows you to generate a
                true copy of the original filesystem for use in
                circumstances when the original version will not be
                used again such as when trying to copy a filesystem
                from disks that are going bad.  The progress reported
                by xfs_copy is also more accurate and files created by
                xfs_copy (target filesystem images and log files) are
                now created with mode 644 (read-write by owner,
                readable by everyone else) (rfe #327721).
    
              o A crash in xfs_bmap_btree_to_extents is possible in the
                presence of user-level attribute usage.  The bug may
                leave a file (which may never have had attributes) in a
                slightly inconsistent state, causing the crash.  Such
                files may be removed or truncated safely, but they may
    
    
                not be read without causing a crash.  The patch
                contains a newer version of xfs_check, which reports
                the problem, as well the kernel fixes for the problem
                (bug #362841).
    
              o If xfsrestore is used to restore a sparse file with a
                hole at the very end of the file, it will not set the
                length of the file correctly if it has to create the
                file or if it has to overwrite a file and the file
                being overwritten is shorter than the file being
                restored (bug #364404).
    
              o If multiple filesystems with the same unique ID (caused
                by a bug in the unique ID generation code), are mounted
                and exported via NFS, the exports will not work
                correctly.  This change updates the unique IDs that are
                duplicated (bug #365043).
    
    
    1.10 Subsystems Included in Patch SG0003289
           This patch release includes these subsystems:
    
              o patchSG0003289.dev_man.irix_lib
    
              o patchSG0003289.eoe_hdr.lib
    
              o patchSG0003289.eoe_man.unix
    
              o patchSG0003289.eoe_sw.dmi
    
              o patchSG0003289.eoe_sw.irix_lib
    
              o patchSG0003289.eoe_sw.quotas
    
              o patchSG0003289.eoe_sw.unix
    
              o patchSG0003289.eoe_sw.xfs
    
              o patchSG0003289.eoe_sw.xfsrt
    
    
    1.11 Installation Instructions
           Because you want to install only the patches for problems
           you have encountered, patch software is not installed by
           default.  After reading the descriptions of the bugs fixed
           in this patch (see Section 1.3), determine the patches that
           meet your specific needs.
    
           If, after reading Sections 1.1 and 1.2 of these release
           notes, you are unsure whether your hardware and software
    
    
           meet the requirements for installing a particular patch, run
           inst.  The inst program does not allow you to install
           patches that are incompatible with your hardware or
           software.
    
           Patch software is installed like any other Silicon Graphics
           software product.  Follow the instructions in your Software
           Installation Administrator's Guide to bring up the miniroot
           form of the software installation tools.
    
           Follow these steps to select a patch for installation:
    
             1.  At the Inst> prompt, type
    
                 install patchSGxxxxxxx
    
                 where xxxxxxx is the patch number.
    
             2.  Initiate the installation sequence. Type
    
                 Inst> go
    
             3.  You may find that two patches have been marked as
                 incompatible.  (The installation tools reject an
                 installation request if an incompatibility is
                 detected.)  If this occurs, you must deselect one of
                 the patches.
    
                 Inst> keep patchSGxxxxxxx
    
                 where xxxxxxx is the patch number.
    
             4.  After completing the installation process, exit the
                 inst program by typing
    
                 Inst> quit
    
    
    1.12 Patch Removal Instructions
           To remove a patch, use the versions remove command as you
           would for any other software subsystem.  The removal process
           reinstates the original version of software unless you have
           specifically removed the patch history from your system.
    
           versions remove patchSGxxxxxxx
    
           where xxxxxxx is the patch number.
    
    
           To keep a patch but increase your disk space, use the
           versions removehist command to remove the patch history.
    
           versions removehist patchSGxxxxxxx
    
           where xxxxxxx is the patch number.
    
    
    1.13 Known Problems
           If a miniroot is booted while quotas are turned on for the
           root filesystem, quotas on the root filesystem will be
           turned off. The system administrator must go through the
           procedure that was described in Section 1.4 and turn quotas
           on again.
    
    

    INST SUBSYSTEM REQUIREMENTS
    No Requirements Information Available.
    

    INST SUBSYSTEM CHECKSUMS

    These checksums help to provide a 'signature' for the patch inst image which can be used to authenticate other inst images. You can obtain this kind of output by running sum -r on the image (from the command line):

    54647     17 ./patchSG0003289.eoe_hdr
    17563    192 ./patchSG0003289.eoe_man
    25049     47 ./patchSG0003289.dev_man
    27071     85 ./README
    25074  13762 ./patchSG0003289.eoe_sw
    65173   4626 ./miniroot/unix.IP22
    22274   4146 ./miniroot/unix.IP20
    18794   9028 ./miniroot/unix.IP21
    62297   7483 ./miniroot/unix.IP26
    10313   9295 ./miniroot/unix.IP25
    30867   7952 ./miniroot/unix.IP28
    40784   9715 ./miniroot/unix.IP19
    27071     85 ./README.patch.3289
    51746     29 ./patchSG0003289
    56219     52 ./patchSG0003289.idb
    

    INST SUBSYSTEM FILE LISTINGS

    The following lists the files which get installed from each subsystem in the patch:

    patchSG0003289.dev_man.irix_lib
    usr/share/catman/p_man/cat2/standard/fcntl.z
    usr/share/catman/p_man/cat2/standard/quotactl.z

    patchSG0003289.eoe_hdr.lib
    usr/include/sys/dmi.h

    patchSG0003289.eoe_man.unix
    usr/share/catman/a_man/cat1/edquota.z
    usr/share/catman/a_man/cat1/mkfs_xfs.z
    usr/share/catman/a_man/cat1/quot.z
    usr/share/catman/a_man/cat1/quotacheck.z
    usr/share/catman/a_man/cat1/quotaon.z
    usr/share/catman/a_man/cat1/repquota.z
    usr/share/catman/a_man/cat1/xfs_bmap.z
    usr/share/catman/a_man/cat1/xfs_check.z
    usr/share/catman/a_man/cat1/xfs_chver.z
    usr/share/catman/a_man/cat1/xfs_copy.z
    usr/share/catman/a_man/cat1/xfs_logprint.z
    usr/share/catman/a_man/cat1/xfs_ncheck.z
    usr/share/catman/a_man/cat1/xfs_repair.z
    usr/share/catman/a_man/cat1/xfsdump.z
    usr/share/catman/a_man/cat1/xfsinvutil.z
    usr/share/catman/a_man/cat1/xfsrestore.z
    usr/share/catman/p_man/cat4/quotas.z
    usr/share/catman/u_man/cat1/quota.z

    patchSG0003289.eoe_sw.dmi
    usr/cpu/sysgen/IP17boot/dmi.a
    usr/cpu/sysgen/IP17boot/dmiidbg.o
    usr/cpu/sysgen/IP19boot/dmi.a
    usr/cpu/sysgen/IP19boot/dmiidbg.o
    usr/cpu/sysgen/IP20boot/dmi.a
    usr/cpu/sysgen/IP20boot/dmiidbg.o
    usr/cpu/sysgen/IP21boot/dmi.a
    usr/cpu/sysgen/IP21boot/dmiidbg.o
    usr/cpu/sysgen/IP22boot/dmi.a
    usr/cpu/sysgen/IP22boot/dmiidbg.o
    usr/cpu/sysgen/IP25boot/dmi.a
    usr/cpu/sysgen/IP25boot/dmiidbg.o
    usr/cpu/sysgen/IP26boot/dmi.a
    usr/cpu/sysgen/IP26boot/dmiidbg.o
    usr/cpu/sysgen/IP28boot/dmi.a
    usr/cpu/sysgen/IP28boot/dmiidbg.o
    usr/lib/libdm.so
    usr/lib64/libdm.so

    patchSG0003289.eoe_sw.irix_lib
    usr/lib32/libdm.so

    patchSG0003289.eoe_sw.quotas
    usr/bsd/quota
    usr/cpu/sysgen/IP17boot/quotas.o
    usr/cpu/sysgen/IP17boot/xfsquotas.a
    usr/cpu/sysgen/IP19boot/quotas.o
    usr/cpu/sysgen/IP19boot/xfsquotas.a
    usr/cpu/sysgen/IP20boot/quotas.o
    usr/cpu/sysgen/IP20boot/xfsquotas.a
    usr/cpu/sysgen/IP21boot/quotas.o
    usr/cpu/sysgen/IP21boot/xfsquotas.a
    usr/cpu/sysgen/IP22boot/quotas.o
    usr/cpu/sysgen/IP22boot/xfsquotas.a
    usr/cpu/sysgen/IP25boot/quotas.o
    usr/cpu/sysgen/IP25boot/xfsquotas.a
    usr/cpu/sysgen/IP26boot/quotas.o
    usr/cpu/sysgen/IP26boot/xfsquotas.a
    usr/cpu/sysgen/IP28boot/quotas.o
    usr/cpu/sysgen/IP28boot/xfsquotas.a
    usr/etc/edquota
    usr/etc/quot
    usr/etc/quotacheck
    usr/etc/quotaon
    usr/etc/repquota

    patchSG0003289.eoe_sw.unix
    etc/init.d/filesystems
    usr/cpu/sysgen/IP17boot/dmistubs.a
    usr/cpu/sysgen/IP17boot/xfsquotasstubs.a
    usr/cpu/sysgen/IP17boot/xfsrtstubs.a
    usr/cpu/sysgen/IP17boot/xfsstubs.a
    usr/cpu/sysgen/IP19boot/dmistubs.a
    usr/cpu/sysgen/IP19boot/xfsquotasstubs.a
    usr/cpu/sysgen/IP19boot/xfsrtstubs.a
    usr/cpu/sysgen/IP19boot/xfsstubs.a
    usr/cpu/sysgen/IP20boot/dmistubs.a
    usr/cpu/sysgen/IP20boot/xfsquotasstubs.a
    usr/cpu/sysgen/IP20boot/xfsrtstubs.a
    usr/cpu/sysgen/IP20boot/xfsstubs.a
    usr/cpu/sysgen/IP21boot/dmistubs.a
    usr/cpu/sysgen/IP21boot/xfsquotasstubs.a
    usr/cpu/sysgen/IP21boot/xfsrtstubs.a
    usr/cpu/sysgen/IP21boot/xfsstubs.a
    usr/cpu/sysgen/IP22boot/dmistubs.a
    usr/cpu/sysgen/IP22boot/xfsquotasstubs.a
    usr/cpu/sysgen/IP22boot/xfsrtstubs.a
    usr/cpu/sysgen/IP22boot/xfsstubs.a
    usr/cpu/sysgen/IP25boot/dmistubs.a
    usr/cpu/sysgen/IP25boot/xfsquotasstubs.a
    usr/cpu/sysgen/IP25boot/xfsrtstubs.a
    usr/cpu/sysgen/IP25boot/xfsstubs.a
    usr/cpu/sysgen/IP26boot/dmistubs.a
    usr/cpu/sysgen/IP26boot/xfsquotasstubs.a
    usr/cpu/sysgen/IP26boot/xfsrtstubs.a
    usr/cpu/sysgen/IP26boot/xfsstubs.a
    usr/cpu/sysgen/IP28boot/dmistubs.a
    usr/cpu/sysgen/IP28boot/xfsquotasstubs.a
    usr/cpu/sysgen/IP28boot/xfsrtstubs.a
    usr/cpu/sysgen/IP28boot/xfsstubs.a
    usr/include/sys/fcntl.h
    usr/include/sys/quota.h
    usr/relnotes/patchSG0003289/TC
    usr/relnotes/patchSG0003289/ch1.z
    var/sysgen/mtune/xfs

    patchSG0003289.eoe_sw.xfs
    sbin/mkfs_xfs
    sbin/mkfs_xfs
    sbin/xfsrestore
    usr/cpu/sysgen/IP17boot/xfs.a
    usr/cpu/sysgen/IP17boot/xfsidbg.o
    usr/cpu/sysgen/IP19boot/xfs.a
    usr/cpu/sysgen/IP19boot/xfsidbg.o
    usr/cpu/sysgen/IP20boot/xfs.a
    usr/cpu/sysgen/IP20boot/xfsidbg.o
    usr/cpu/sysgen/IP21boot/xfs.a
    usr/cpu/sysgen/IP21boot/xfsidbg.o
    usr/cpu/sysgen/IP22boot/xfs.a
    usr/cpu/sysgen/IP22boot/xfsidbg.o
    usr/cpu/sysgen/IP25boot/xfs.a
    usr/cpu/sysgen/IP25boot/xfsidbg.o
    usr/cpu/sysgen/IP26boot/xfs.a
    usr/cpu/sysgen/IP26boot/xfsidbg.o
    usr/cpu/sysgen/IP28boot/xfs.a
    usr/cpu/sysgen/IP28boot/xfsidbg.o
    usr/sbin/xfs_bmap
    usr/sbin/xfs_check
    usr/sbin/xfs_chver
    usr/sbin/xfs_copy
    usr/sbin/xfs_db
    usr/sbin/xfs_db
    usr/sbin/xfs_logprint
    usr/sbin/xfs_logprint
    usr/sbin/xfs_ncheck
    usr/sbin/xfs_repair
    usr/sbin/xfsdump
    usr/sbin/xfsinvutil

    patchSG0003289.eoe_sw.xfsrt
    usr/cpu/sysgen/IP17boot/xfsrt.a
    usr/cpu/sysgen/IP19boot/xfsrt.a
    usr/cpu/sysgen/IP20boot/xfsrt.a
    usr/cpu/sysgen/IP21boot/xfsrt.a
    usr/cpu/sysgen/IP22boot/xfsrt.a
    usr/cpu/sysgen/IP25boot/xfsrt.a
    usr/cpu/sysgen/IP26boot/xfsrt.a
    usr/cpu/sysgen/IP28boot/xfsrt.a


    DOWNLOAD PATCH
    Download Server File Name Date Added Size Download
    download.sgi.com patchSG0003289.tar 15-Oct-1998 61 Mb FTP HTTP Add to download cart 
    download.sgi.com patchSG0003289.tardist 15-Oct-1998 61 Mb FTP HTTP
     
    FTP = download using FTP protocol
    HTTP = download using HTTP protocol
    Add to shopping list= store in your basket for downloading later
  •  


    Document Id: 20021117072512-IRIXPatch-1282