Abstract:
A serverless distributed file system manages the storage of files and directories using one or more directory groups. The directories may be managed using Byzantine-fault-tolerant groups, whereas files are managed without using Byzantine-fault-tolerant groups. Additionally, the file system may employ a hierarchical namespace to store files. Furthermore, the directory group may employ a plurality of locks to control access to objects (e.g., files and directories) in each directory.
Abstract:
Apparatus and method insuring that data objects used to maintain state information for shared data at a local central processing complex (CPC) is coherent with respect to state information maintained at a structured external storage facility (SES) over a link is valid. An error detector is attached to the CPC side of the link for detecting errors on the link, and, when an error is detected, setting a error state pending (ESP) latch to indicate that the link has failed and that the shared data in the local data object may be invalid because a message invalidating the data may not have been received by the CPC. In data processing operations, the ESP latch is interrogated by a central processor in the CPC to determine the health of the message path to the SES facility. A local cache vector reflecting the validity of the shared data in the local cache may then be interrogated to determine if the shared data in the local cache is valid. If a healthy path has continuously existed and the vector indicates that the local cache data is valid, the integrity of the data can be relied on.
Abstract:
In a multi-system data sharing complex 10, 12, 13, a database system can write updated pages to a shared electronic store 16, for a fast write. Other database systems can obtain pages written to the shared store for further modification without the pages first being written to stable storage 14, 15. However, pages are eventually written to the stable storage in a castout process. Recovery of a database from failure of the shared store is bounded by determination of a recovery boundary which, when applied to the union of database system transaction logs, establishes a point in front of which are found log records of modifications to pages which were in the shared store when it failed. These log records are applied to page versions obtained from stable storage to recover from failure of the shared store.
Abstract:
The present invention provides a technique for processing a lock request. A first lock server is a takeover lock server of a second lock server. The first lock server enters a silent state after learning that a fault occurs in the second lock server, where a silent range is a resource for which the second lock server has assigned permission. The first lock server receives an acquire lock request that is originally sent to the second lock server, and the first lock server assigns lock permission for a corresponding resource according to the acquire lock request if the second lock server has not assigned resource for the resource. By means of this solution, an impact range of a fault occurring in a lock server can be reduced, and stability of a lock management system is improved.
Abstract:
A data mirroring control apparatus includes a command distributing unit configured to transmit a first write command to a plurality of mirroring storage devices, the first write command including an instruction for data requested by a host to be written; and a memory lock setting unit configured to set a memory lock on the data requested by the host to be written among data stored in a host memory and configured to release the memory lock on the data after the data with the memory lock is written to the plurality of mirroring storage devices.
Abstract:
A data processing system participating in two-phase transaction processing operations which, when a system failure occurs while one or more transactions are in process, can successfully rebuild "in-doubt" states even when another system failure occurs during an attempt to effect the rebuild. The system includes a file management system having exclusive access to reserved locations in the memory for reading and writing meta-data therein and physical file access logic selectively coupling the memory and the database access application, the physical file access logic incorporating file protections which are controlled by the file management system; such that, in the event of a failure, the local state of the transaction can be faithfully rebuilt after restart by accessing the meta-data. Upon restart after a failure, the results of incomplete non-"in-doubt" transactions are removed, the files which have been updated by "in-doubt" transactions are locked and normal access to the affected database is then permitted.
Abstract:
A data processing system participating in two-phase transaction processing operations which, when a system failure occurs while one or more transactions are in process, can successfully rebuild "in-doubt" states even when another system failure occurs during an attempt to effect the rebuild. The system includes a file management system having exclusive access to reserved locations in the memory for reading and writing meta-data therein and physical file access logic selectively coupling the memory and the database access application, the physical file access logic incorporating file protections which are controlled by the file management system; such that, in the event of a failure, the local state of the transaction can be faithfully rebuilt after restart by accessing the meta-data. Upon restart after a failure, the results of incomplete non-"in-doubt" transactions are removed, the files which have been updated by "in-doubt" transactions are locked and normal access to the affected database is then permitted.
Abstract:
A data processing system participating in two-phase transaction processing operations which, when a system failure occurs while one or more transactions are in process, can successfully rebuild "in-doubt" states even when another system failure occurs during an attempt to effect the rebuild. The system includes a file management system having exclusive access to reserved locations in the memory for reading and writing meta-data therein and physical file access logic selectively coupling the memory and the database access application, the physical file access logic incorporating file protections which are controlled by the file management system; such that, in the event of a failure, the local state of the transaction can be faithfully rebuilt after restart by accessing the meta-data. Upon restart after a failure, the results of incomplete non-"in-doubt" transactions are removed, the files which have been updated by "in-doubt" transactions are locked and normal access to the affected database is then permitted.
Abstract:
Während der Sicherung von in einzelnen Dateien abgelegten Daten einer Datenbank ist aus Konsistenzgründen eine Veränderung der Daten in den einzelnen Dateien nicht zulässig. Aus diesem Grund werden die Dateien ab einem bestimmten Zeitpunkt während eines Sicherungslaufes für verändernde Zugriffe gesperrt. Erfindungsgemäß wird der Sicherungslauf in zwei Schritten durchgeführt. Im ersten Schritt werden die Dateien übertragen, ohne daß eine Veränderungssperre besteht. In einer Aufzeichnungsdatei werden alle Dateien vermerkt, die während des ersten Schrittes verändert werden. Diese Dateien werden in einem zweiten Schritt erneut übertragen. Nur während des zweiten Schrittes ist eine Veränderungssperre erforderlich. Leistung und Funktionsfähigkeit des auf die Datenbank zugreifenden Systems werden durch das erfindungsgemäße Verfahren nur geringfügig beeinträchtigt. Es ist davon auszugehen, daß die Anzahl der im zweiten Schritt zu übertragenden Dateien sehr viel kleiner ist als die Anzahl der im ersten Schritt zu übertragenden Dateien. Daher wird eine wesentlich verkürzte Veränderungssperre erreicht.