Patent application number | Description | Published |
20130000183 | CATALYST FOR THERMOCATALYTIC CONVERSION OF BIOMASS TO LIQUID FUELS AND CHEMICALS - Catalyst compositions comprising a phosphorous-promoted ZSM-5 component and a silica-containing binder, and methods for making and using same, are disclosed. More specifically, processes for making a catalyst for biomass conversion are provided. The process includes: treating a ZSM-5 zeolite with a phosphorous-containing compound to form a phosphorous-promoted ZSM-5 component; preparing a slurry comprising the phosphorous-promoted ZSM-5 component and a silica-containing binder; and shaping the slurry into shaped bodies. Such catalysts can be used for the thermocatalytic conversion of particulate biomass to liquid products such as bio-oil, resulting in higher bio-oil yields and lower coke than conventional catalysts. | 01-03-2013 |
20130232855 | Two-Stage Reactor And Process For Conversion Of Solid Biomass Material - A two-stage reactor/process is disclosed for the conversion of solid particulate biomass material and includes: a first stage, in which solid particulate biomass material is pyrolyzed to primary reaction products, and a second stage in which the primary reaction products are catalytically converted in a second stage which is operated at a temperature higher than that of the first stage. | 09-12-2013 |
20140024866 | Catalysts for Thermo-Catalytic Conversion of Biomass, and Methods of Making and Using - Disclosed are catalyst compositions including zeolite and silica components, methods of making, and processes of using in the thermo-catalytic conversion of biomass. Such disclosed methods of making include: i) spray drying of the catalyst precursor slurry at a pH below 1, or ii) the removal of ions such as sodium from the binder material prior to spray drying the catalyst precursor slurry at a pH below 2.7, or iii) spray drying the catalyst precursor including a pore regulating agent followed by steam treating, or iv) some combination of i), ii) and iii). | 01-23-2014 |
20140275588 | Phosphorous Promotion of Zeolite-Containing Catalysts - Disclosed are methods of making, and processes of using phosphorous-promoted zeolite-containing catalysts in the conversion of hydrocarbonaceous materials such as hydrocarbons and biomass. Such disclosed methods of making include: spray drying of the catalyst precursor slurry followed by phosphorous promotion of the resulting spray dried material. | 09-18-2014 |
20150045208 | Catalysts For Thermo-Catalytic Conversion Of Biomass, And Methods Of Making and Using - Disclosed are catalyst compositions including zeolite and silica components, methods of making, and processes of using in the thermo-catalytic conversion of biomass. Such disclosed methods of making include treating the zeolite with phosphorous during formation of the catalyst rather than prior to or after catalyst formation. | 02-12-2015 |
20150202615 | PROCESS OF REACTIVATING A METAL CONTAMINATED BIOMASS CONVERSION CATALYST - A metal contaminated spent catalyst or regenerated catalyst from a biomass conversion unit may be subjected to an ammonium wash in order to remove potassium. The ammonium wash may include ammonium sulfate, ammonium nitrate, ammonium hydroxide, ammonium acetate, ammonium phosphates, and mixtures thereof. Acidity and catalytic activity of the biomass conversion catalyst is restored by the removal of potassium contaminants. | 07-23-2015 |
20150231613 | CATALYST FOR THERMOCATALYTIC CONVERSION OF BIOMASS TO LIQUID FUELS AND CHEMICALS - Catalyst compositions comprising a phosphorous-promoted ZSM-5 component and a silica-containing binder, and methods for making and using same, are disclosed. More, specifically, processes for making a catalyst for biomass conversion are provided. The process includes: treating a ZSM-5 zeolite with a phosphorous-containing compound to form a phosphorous-promoted ZSM-5 component; preparing a slurry comprising the phosphorous-promoted ZSM-5 component and a silica-containing binder; and shaping the slurry into shaped bodes. Such catalysts can be used for the Thermocatalytic conversion of particulate biomass to liquid products such as bio-oil, resulting in higher bio-oil yields and lower coke than conventional catalysts. | 08-20-2015 |
Patent application number | Description | Published |
20080301203 | MANAGING A SNAPSHOT STORED WITHIN A FILE SYSTEM SPACE FOR EFFICIENT DETECTING OF IN-USE BLOCKS - In one embodiment, at least one snapshot thread manages a point in time snapshot of a file system stored within the space allocated to the file system. The snapshot thread tracks, for at least one block of the plurality of blocks of the file system, a separate entry in a snapshot map specifying if each at least one block is newly allocated following the creation of the point in time snapshot and specifying an addressed location of a snapshot copy of the at least one block if copied. Separately, a file system handling thread tracks a mapping of an allocation state of each of said plurality of blocks of the file system. Responsive to detecting the file system triggered to write or delete a particular block from among the at least one block of the file system, the snapshot thread allows the file system to write to or delete the particular block without making a snapshot copy of the particular block if a particular entry for the particular block in the snapshot map specifies the particular block is newly allocated, wherein a block marked newly allocated was not in-use at the point in time of the file system snapshot. | 12-04-2008 |
20100250493 | USING A SPARSE FILE AS A CLONE OF A FILE - One embodiment is for using a sparse file as a clone. The method includes creating, by an application associated with a computer system, a snapshot of a file, such as an individual file, a collection of files, file system, directories, and so forth. Further, the method includes requesting, by the application, a clone of that created snapshot. Further still, the method includes generating, by the application, an empty sparse having at least one inode identifying the empty sparse file as the clone and pointing to the snapshot associated with the clone. Thereby, the requested clone is created using the created sparse file, which begins as an empty sparse file. | 09-30-2010 |
20120005162 | Managing Copies of Data Structures in File Systems - A method, data processing system, and computer program product for managing data. A processor unit copies a data structure within a hierarchy of data structures to form a copy of the data structure. The data structure belongs to a level within a plurality of levels in the hierarchy of data structures. The processor unit associates an identifier with the data structure within the hierarchy of data structures. The processor unit increments a portion of the identifier for the data structure in response to copying the data structure to form the copy of the data structure and associating the identifier with the data structure within the hierarchy of data structures. The portion of the identifier that is incremented is based on the level within the plurality of levels in which the data structure is located. | 01-05-2012 |
20120066181 | FILE REMOVAL WITH NO AVAILABLE DISK BLOCKS IN REDIRECT-ON-WRITE FILE SYSTEMS - Embodiments include a method for removing a file within a redirect-on-write file system. In some embodiments, a file removal operation is detected in a file management unit, which resides in a memory unit. It is then determined that the number of free data blocks in the persistent storage is below a minimum threshold. The file removal operation is written to a log used for storing system operations. A file management unit is notified of the successful write of the file removal operation to the log used for storing system operations. The data blocks are moved from the file selected for removal to a list of free data blocks. The indirect blocks from the file selected for removal are moved to a data block removal list. | 03-15-2012 |
20120066183 | FILE CLONING ACROSS DIFFERENT FILESETS - After a clone file is created from a file, a write request targeting the clone file can be handled. It is determined that the write request indicates the clone file that was cloned from a file in a first fileset. The clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset. A data block of the clone file affected by the write request is determined. It is then determined that the data block at a current location cannot be modified. The write request is implemented with respect to the data block at a different location. It is indicated that the data block at the different location can be modified for subsequent write requests that indicate the clone file | 03-15-2012 |
20120066190 | HANDLING FILE OPERATIONS WITH LOW PERSISTENT STORAGE SPACE - In some embodiments, a file management unit located in the operating system detects a write operation that writes the data blocks within the consistency snapshot (in main memory) to the persistent storage. The file management unit can then determine that all transactions have been completed before the write operation begins. In some instances, the file management unit then attempts to write the data blocks within the consistency snapshot to the persistent storage. The file management unit can then receive a notification that the write operation did not successfully write the data blocks from the consistency snapshot to the persistent storage. In some embodiments, the write operation is not successful because there are fewer free data blocks in the persistent storage than needed for writing the data blocks within the consistency snapshot to persistent storage. The file management can then wait a period of time. After the file management unit has waited for a period of time, it can make another attempt to write the data blocks within the consistency snapshot to the persistent storage. | 03-15-2012 |
20120066278 | DISTRIBUTED FILE HIERARCHY MANAGEMENT IN A CLUSTERED REDIRECT-ON-WRITE FILE SYSTEM - Management of a file hierarchy for a clustered file system can be distributed across nodes of the cluster. A cluster file hierarchy is accessed to determine location of a file in response to a request to write to a file. A first node maintains the cluster file hierarchy. It is determined that management of a fileset object, which represents a fileset that includes the file, has been delegated to a second node based, at least in part, on said accessing the cluster file hierarchy. A node file hierarchy maintained by the second node is accessed responsive to determining the delegation. The cluster file hierarchy represents filesets of the clustered file system and the node hierarchy represents a subset of one or more of the filesets. Location of the file is determined based, at least in part, on said accessing the node file hierarchy. | 03-15-2012 |
20120150800 | INDEPENDENT FILESET GENERATIONS IN A CLUSTERED REDIRECT-ON-WRITE FILESYSTEM - Maintaining a generation value for each fileset that is distinct from a corresponding fileset manager preserves the independence of nodes while also allowing distributed fileset management. A fileset manager can maintain a value that reflects consistency snapshots for that node (“node generation”) separately from a value that reflects consistency snapshots for a particular fileset (“fileset generation”). | 06-14-2012 |
20120150804 | MULTIPLE CONTEXTS IN A REDIRECT ON WRITE FILE SYSTEM - A method includes initiating committing to persistent storage of a current consistency snapshot of a plurality of data objects in a redirect-on-write file system. Each of the plurality of data objects has a first copy of at least two copies of the data having a first context of at least two contexts. The method includes receiving, during committing to storage of the current consistency snapshot, an update to a data object of the plurality of data objects. The method also includes responsive to receipt of the update to the data object, creating a second copy of data of the data object from the first copy. The second copy of the data has a second context of the at least two contexts. The method includes responsive to receipt of the update to the data object, updating, based on the update, the second copy of the data of the data object. | 06-14-2012 |
20120150926 | DISTRIBUTED FREE BLOCK MAP FOR A CLUSTERED REDIRECT-ON-WRITE FILE SYSTEM - In a cluster that distributes fileset management, fileset managers will maintain a free block map and an in-flight block map to allocate blocks to clients writing to a relevant fileset. A fileset manager managing free block allocation for cluster clients that write to a fileset managed by the fileset manager. Since a clustered file system manager manages an initial free block map for the cluster (“cluster free block map”), the clustered file system manager provisions free blocks to fileset managers from the cluster free block map. The fileset manager then allocates free blocks from the provisioned free blocks to cluster clients that write to the fileset managed by the fileset manager. | 06-14-2012 |
20120209810 | Using a Sparse File as a Clone of a File - One embodiment is for using a sparse file as a clone. The method includes creating, by an application associated with a computer system, a snapshot of a file, such as an individual file, a collection of files, file system, directories, and so forth. Further, the method includes requesting, by the application, a clone of that created snapshot. Further still, the method includes generating, by the application, an empty sparse having at least one inode identifying the empty sparse file as the clone and pointing to the snapshot associated with the clone. Thereby, the requested clone is created using the created sparse file, which begins as an empty sparse file. | 08-16-2012 |
20120209813 | FILE CLONING ACROSS DIFFERENT FILESETS - After a clone file is created from a file, a write request targeting the clone file can be handled. It is determined that the write request indicates the clone file that was cloned from a file in a first fileset. The clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset. A data block of the clone file affected by the write request is determined. It is then determined that the data block at a current location cannot be modified. The write request is implemented with respect to the data block at a different location. It is indicated that the data block at the different location can be modified for subsequent write requests that indicate the clone file | 08-16-2012 |
20120284230 | Importing Pre-Existing Data of a Prior Storage Solution into a Storage Pool for Use with a New Storage Solution - Mechanisms are provided for importing pre-existing data into a storage system utilizing a current storage management system that is different from an original storage management system used to create the pre-existing data. One or more data storage devices are integrated into the storage system in-place without modification of the pre-existing data stored on the one or more data storage devices. Metadata for the pre-existing data is created based on a linear progression of data in the pre-existing data. Read access requests targeting the pre-existing data are executed using the created metadata. Write access requests targeting the pre-existing data are executed by redirecting the write access requests to a copy of the pre-existing data created in another storage location. | 11-08-2012 |
20120284309 | Importing Pre-Existing Data of a Prior Storage Solution into a Storage Pool for Use with a New Storage Solution - Mechanisms are provided for importing pre-existing data into a storage system utilizing a current storage management system that is different from an original storage management system used to create the pre-existing data. One or more data storage devices are integrated into the storage system in-place without modification of the pre-existing data stored on the one or more data storage devices. Metadata for the pre-existing data is created based on a linear progression of data in the pre-existing data. Read access requests targeting the pre-existing data are executed using the created metadata. Write access requests targeting the pre-existing data are executed by redirecting the write access requests to a copy of the pre-existing data created in another storage location. | 11-08-2012 |
20130031058 | MANAGING DATA ACCESS REQUESTS AFTER PERSISTENT SNAPSHOTS - A client node on which a file system is mounted can be configured to efficiently handle content access requests after a snapshot is created. The client node can maintain generation numbers at a data block, a file, and a fileset level to determine whether a data block is part of a snapshot generation and consequently whether the data block is writable in a current generation. Data block mappings and write access permissions associated with the data blocks need not be revoked at the client node prior to creating the snapshot. Cached data block mappings can be accessed to identify data blocks for servicing a read request. The data block can be updated in place if the data block is not part of the snapshot generation. The write request can be serviced at a new data block if the data block is part of the snapshot generation. | 01-31-2013 |
20130047043 | MERGING MULTIPLE CONTEXTS TO MANAGE CONSISTENCY SNAPSHOT ERRORS - A method including creating a commit-in-progress context from a copy of a data object in a redirect-on-write file system; and begin storing the commit-in-progress context in a persistent storage device. The method further includes, while storing the commit-in-progress context in the persistent storage device: receiving a notification of a pending modification to the first data object, creating an update-in-progress context from a copy of the commit-in-progress context, and begin applying the modification to the update-in-progress context. The method further includes detecting that a connectivity error has occurred between the commit-in-progress context and the storage device, and in response, identifying whether the commit-in-progress context is successfully stored in the storage device. In response to identifying that the commit-in-progress context is not successfully stored: aborting the storing of the commit-in-progress context, assigning a new commit-in-progress context, and begin storing the new commit-in-progress context. | 02-21-2013 |
20130318086 | DISTRIBUTED FILE HIERARCHY MANAGEMENT IN A CLUSTERED REDIRECT-ON-WRITE FILE SYSTEM - Management of a file hierarchy for a clustered file system can be distributed across nodes of the cluster. A cluster file hierarchy is accessed to determine location of a file in response to a request to write to a file. A first node maintains the cluster file hierarchy. It is determined that management of a fileset object, which represents a fileset that includes the file, has been delegated to a second node based, at least in part, on said accessing the cluster file hierarchy. A node file hierarchy maintained by the second node is accessed responsive to determining the delegation. The cluster file hierarchy represents filesets of the clustered file system and the node hierarchy represents a subset of one or more of the filesets. Location of the file is determined based, at least in part, on said accessing the node file hierarchy. | 11-28-2013 |
20140156602 | FILE CLONING ACROSS DIFFERENT FILESETS - A method includes determining, by a processor, that a write request indicates a clone file that was cloned from a file in a first fileset. The clone file is of a second fileset and a clustered file system comprises the first fileset and the second fileset. A data block of the clone file affected by the write request is determined. The method includes determining that the data block at a current location cannot be modified. In response to a determination that the data block at the current location cannot be modified, the method includes implementing the write request with respect to the data block at a different location and indicating that the data block at the different location can be modified for subsequent write requests that indicate the clone file. | 06-05-2014 |
20150178297 | Method to Preserve Shared Blocks when Moved - A method, system and computer-usable medium are disclosed for tracking blocks moved within a file system, comprising: associating tracking information with a base object within the file system; tracking movement of the base object via the tracking information; and, adjusting information relating to an associated object of the base object derived from the base object. | 06-25-2015 |
Patent application number | Description | Published |
20080222211 | Method and Apparatus to Capture and Transmit Dense Diagnostic Data of a File System - A processor selects file system metadata. A processor identifies each unit of data in a file system. The processor determines if the unit of data contains file system metadata. The processor writes a unit of data of metadata to a diagnostic file system, provided it was determined that the unit of data contains file system metadata. The processor then determines if the unit of data contains user data. If the unit of data contains user data, the processor writes a sparse object to the diagnostic file. | 09-11-2008 |
20080288546 | METHOD AND SYSTEM FOR HANDLING REALLOCATED BLOCKS IN A FILE SYSTEM - A system for managing a file system. In response to a user selecting an image of the file system to perform a rollback operation, each data block in the file system that is owned by the image is searched for. Then, it is determined whether a data block owned by the image is marked in a first map and a second map. In response to determining that the data block owned by the image is marked in the first map and the second map, the data block is marked in a third map. In response to determining that the data block owned by the image is marked in the third map, a new data block is allocated in the file system. Subsequently, data from the data block owned by the image is copied to the new data block in the file system prior to performing the rollback operation to avoid a collision that causes data corruption. | 11-20-2008 |
20090049068 | Method and Apparatus to Capture and Transmit Dense Diagnostic Data of a File System - A processor selects file system metadata. A processor identifies each unit of data in a file system. The processor determines if the unit of data contains file system metadata. The processor writes a unit of data of metadata to a diagnostic file system, provided it was determined that the unit of data contains file system metadata. The processor then determines if the unit of data contains user data. If the unit of data contains user data, the processor writes a sparse object to the diagnostic file. | 02-19-2009 |
20090070535 | HANDLING TEMPORARY FILES IN A FILE SYSTEM WITH SNAPSHOTS - A temporary file is identified. The temporary file includes a data block containing a first file image. A determination is made whether the temporary block has been included in a previous snapshot. Responsive to receiving a modification of the temporary block that has been included in the previous snapshot, a modified first image is created. The modified image is stored in the original file block, and the original image is copied to a newly allocated block. The original first block is updated to include a reference to the second block. | 03-12-2009 |
20100011035 | Method and System for Handling Reallocated Blocks in a File System - A system for managing a file system. In response to a user selecting an image of the file system to perform a rollback operation, each data block in the file system that is owned by the image is searched for. Then, it is determined whether a data block owned by the image is marked in a first map and a second map. In response to determining that the data block owned by the image is marked in the first map and the second map, the data block is marked in a third map. In response to determining that the data block owned by the image is marked in the third map, a new data block is allocated in the file system. Subsequently, data from the data block owned by the image is copied to the new data block in the file system prior to performing the rollback operation to avoid a collision that causes data corruption. | 01-14-2010 |