Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.

Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.

Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.

Abstract: A connection state system is described herein that allows a client to resume a connection with a server or a different replacement server by remotely storing client state information in association with a resume key. The system provides a resume key filter operating at the server that facilitates the storing of volatile server state information. The state information can include information such as oplocks, leases granted to a client, and in-flight operations on a file handle. The resume key filter driver sits above the file system, which allows multiple file access protocols to use the filter. Upon a failover event, such as a server going down or losing connectivity to a client, the system can bring up another server or the same server and reestablish state for file handles held by various clients using the resume key filter.

Abstract: An optical disk cassette has a disk eject mechanism that ejects a disk such as a DVD or CD. The disk eject mechanism has pushrod, transfer and kick out portions. The pushrod portion slides relative to a side of the cassette case. Pivotally mounted within the case, the kick out portion pushes a disk to eject it from the case. The transfer portion translates pushrod motion to motion of the kick out portion. In a preferred embodiment, the disk eject mechanism is a unitary body, with pushrod, transfer and kick out portions made homogeneously as a single entity, the pushrod portion being a resilient joining elbow. In another preferred embodiment, the disk eject mechanism has a transfer portion that is a rack and a pinion. The rack extends from the pushrod portion and the pinion is attached to or formed as part of the kick out portion.

Abstract: Described are embodiments directed at persistent handles that are used to retain state across network failures and server failovers. Persistent handles are requested by a client after a session has been established with a file server. The request for the persistent handle includes a handle identifier generated by the client. The server uses the handle identifier to associate with state information. When there is a network failure or a server failover, and a reconnection to the client, the handle identifier is used to identify replayed requests that if replayed would create an inconsistent state on the server. The replayed requests are then appropriately handled.

Abstract: An optical disk mechanism has a housing with at least one disk entry/exit aperture. A disk guide, such as a plate, is aligned with and guides an optical disk through the disk entry/exit aperture. Two beams rotatably support at least one roller and a drive mechanism. Flexing and biasing the roller towards the disk, the two beams maintain a rotational axis of the roller parallel to the disk and accommodate varying separation between the roller and the disk guide. The two beams are closely spaced and non-coplanar, and may be part of a double-beam mount. The double-beam mount attaches the two beams to the housing and to a frame, which positions the roller near the disk guide and the disk entry/exit aperture. Sliding the disk along the plate or other disk guide, the roller is reversible to drive the disk in or out through the disk entry/exit aperture.

Abstract: A connection state system is described herein that allows a client to resume a connection with a server or a different replacement server by remotely storing client state information in association with a resume key. The system provides a resume key filter operating at the server that facilitates the storing of volatile server state information. The state information can include information such as oplocks, leases granted to a client, and in-flight operations on a file handle. The resume key filter driver sits above the file system, which allows multiple file access protocols to use the filter. Upon a failover event, such as a server going down or losing connectivity to a client, the system can bring up another server or the same server and reestablish state for file handles held by various clients using the resume key filter.

Abstract: An optical disk cassette has a cassette case with a disk retention device. A free end of the disk retention device acts upon an edge of the optical disk, opposably displacing during insertion and ejection of the optical disk. The device and disk are at equilibrium when the free end is displaced by the full diameter of the disk. When the disk is displaced in the insertion or ejection direction, the free end urges the disk in the insertion or ejection direction, assisting with the optical disk insertion or ejection respectively. Embodiments may have the disk retention device including one or more retainers. Each retainer may have a free end and opposing fixed end, and be flexible or have a flexible region. The free end slides along or otherwise contacts the circumferential edge of the optical disk, exerting a force upon it during optical disk insertion, retention and ejection.

Abstract: An optical disk mechanism has a housing with at least one disk entry/exit aperture. A disk guide, such as a plate, is aligned with and guides an optical disk through the disk entry/exit aperture. Two beams rotatably support at least one roller and a drive mechanism. Flexing and biasing the roller towards the disk, the two beams maintain a rotational axis of the roller parallel to the disk and accommodate varying separation between the roller and the disk guide. The two beams are closely spaced and non-coplanar, and may be part of a double-beam mount. The double-beam mount attaches the two beams to the housing and to a frame, which positions the roller near the disk guide and the disk entry/exit aperture. Sliding the disk along the plate or other disk guide, the roller is reversible to drive the disk in or out through the disk entry/exit aperture.

Abstract: An optical disk cassette has a disk eject mechanism that ejects a disk such as a DVD or CD. The disk eject mechanism has pushrod, transfer and kick out portions. The pushrod portion slides relative to a side of the cassette case. Pivotally mounted within the case, the kick out portion pushes a disk to eject it from the case. The transfer portion translates pushrod motion to motion of the kick out portion. In a preferred embodiment, the disk eject mechanism is a unitary body, with pushrod, transfer and kick out portions made homogeneously as a single entity, the pushrod portion being a resilient joining elbow. In another preferred embodiment, the disk eject mechanism has a transfer portion that is a rack and a pinion. The rack extends from the pushrod portion and the pinion is attached to or formed as part of the kick out portion.

Abstract: A method for storing data, comprising the steps of (A) receiving a stream of data, (B) storing the stream of data in a series of data clusters each comprising (i) a predecessor link, (ii) a data portion, and (iii) a successor link, where the predecessor links and successor links are configured to minimize seek time between the clusters during contiguous stream operations.

Abstract: A method of recording Audio-Video Interleaved (AVI) files on a disc, comprising the steps of (a) allocating a predetermined amount of space on the disc as a reserved track, (b) encapsulating audio data and video data into corresponding audio chunks and video chunks to be recorded on the disc, (c) adding a first amount of padding to (i) create a first gap and (ii) position the first gap in relation to the audio chunks and the video chunks in response to completely recording all of the audio chunks and the video chunks, (d) recording data on the reserved track and (e) adding a second amount of padding to (i) create a second gap and (ii) position the second gap in relation to the audio chunks and the video chunks to allow the recording of the Audio-Video Interleaved file to be compliant with a predefined disc standard.

Abstract: A method for storing data, comprising the steps of (A) receiving a stream of data, (B) storing the stream of data in a series of data clusters each comprising (i) a predecessor link, (ii) a data portion, and (iii) a successor link, where the predecessor links and successor links are configured to minimize seek time between the clusters during contiguous stream operations.

Abstract: A method for parking a drive in a video recorder comprising the steps of (A) applying main power to the video recorder, (B) parking the drive in response to applying main power to the video recorder, (C) placing the video recorder in a standby mode, (D) presenting a user with a setup request to (i) setup the video recorder in the standby mode or (ii) enter into a normal mode, (E) if the user selects to setup the video recorder, continue parking the drive, and (F) if the user selects to enter into the normal mode, unparking the drive to allow the video recorder to access the drive.

Abstract: A method for storing data, comprising the steps of (A) receiving a stream of data, (B) storing the stream of data in a series of data clusters each comprising (i) a predecessor link, (ii) a data portion, and (iii) a successor link, where the predecessor links and successor links are configured to minimize seek time between the clusters during contiguous stream operations.

Abstract: A method of recording Audio-Video Interleaved (AVI) files on a disc, comprising the steps of (a) allocating a predetermined amount of space on the disc as a reserved track, (b) encapsulating audio data and video data into corresponding audio chunks and video chunks to be recorded on the disc, (c) adding a first amount of padding to (i) create a first gap and (ii) position the first gap in relation to the audio chunks and the video chunks in response to completely recording all of the audio chunks and the video chunks, (d) recording data on the reserved track and (e) adding a second amount of padding to (i) create a second gap and (ii) position the second gap in relation to the audio chunks and the video chunks to allow the recording of the Audio-Video Interleaved file to be compliant with a predefined disc standard.

Abstract: A method for retroactively recording from a circular buffer comprising the steps of (A) determining a starting point in the circular buffer, (B) generating a linear buffer by breaking the circular buffer before the starting point and (C) appending to an ending point of the linear buffer.

Abstract: An apparatus comprising a first partition and a second partition. The first partition has a first file system comprising (i) a plurality of first clusters configured to store data having accesses faster than a first worst case data transfer rate and (ii) a dedicated space not used by the plurality of first clusters. The second partition has a second file system comprising a plurality of second clusters (i) configured to store data having accesses faster than a second worst case data transfer rate and (ii) occupying the dedicated space.

Abstract: A method for storing data, comprising the steps of (A) receiving a stream of data, (B) storing the stream of data in a series of data clusters each comprising (i) a predecessor link, (ii) a data portion, and (iii) a successor link, where the predecessor links and successor links are configured to minimize seek time between the clusters during contiguous stream operations.