会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 6. 发明授权
    • Inode to pathname support with a hard link database
    • Inode到路径名支持与硬链接数据库
    • US09104675B1
    • 2015-08-11
    • US13461316
    • 2012-05-01
    • Morgan ClarkMichael D. ScheerMichael D. SchoutenJean-Pierre BonoAlexander S. Mathews
    • Morgan ClarkMichael D. ScheerMichael D. SchoutenJean-Pierre BonoAlexander S. Mathews
    • G06F17/30
    • G06F17/30067G06F17/30091
    • For enabling a fast reverse lookup of parent directories storing records of hard links to a specified regular file, a file system manager maintains a hard link database (HLDB) storing information for addressing hard links to the regular files having multiple hard links. The HLDB contains a corresponding HLDB file for each regular file having multiple hard links. In a preferred implementation, the inode of each regular file stores the addressing information for one hard link to the regular file, a corresponding HLDB file stores the addressing information for other hard links to the regular file, each HLDB file is a directory accessed by invoking file system manager directory access routines, and the HLDB has a directory tree providing a multi-level hash index for searching the HLDB given the inode number of a regular file.
    • 为了能够快速反向查找存储到指定常规文件的硬链接记录的父目录,文件系统管理器维护一个硬链接数据库(HLDB),用于存储用于寻址具有多个硬链接的常规文件的硬链接的信息。 HLDB包含每个具有多个硬链接的常规文件的相应HLDB文件。 在优选实现中,每个常规文件的inode将一个硬链接的寻址信息存储到常规文件中,相应的HLDB文件将用于其他硬链接的寻址信息存储到常规文件,每个HLDB文件是通过调用访问的目录 文件系统管理器目录访问例程,并且HLDB具有目录树,其提供用于在给定常规文件的索引节点号的情况下搜索HLDB的多级哈希索引。
    • 7. 发明授权
    • Redundancy check of transaction records in a file system log of a file server
    • 冗余检查文件服务器的文件系统日志中的事务记录
    • US07631009B1
    • 2009-12-08
    • US11619132
    • 2007-01-02
    • Dixit PatelMorgan ClarkJean Pierre Bono
    • Dixit PatelMorgan ClarkJean Pierre Bono
    • G06F17/00
    • G06F11/1004Y10S707/99942Y10S707/99943Y10S707/99945
    • To recover from partial writes of metadata transactions to a file system log, a redundancy check is added to each log record. Upon re-boot of the file server, the file system is recovered by finding the last valid record in the log, and then replaying records from the log into the on-disk file system. The replay is terminated prior to the last valid record upon reaching any record with a bad redundancy check. A “fsck” is performed on the file system prior to granting client access to the file system only if the log recovery was terminated prior to the last valid record upon reaching a record with a bad redundancy check and the position of the records in the log indicates that this record with a bad redundancy check could not have been written to the log concurrently with the last valid record.
    • 要从元数据事务的部分写入恢复到文件系统日志,将向每个日志记录添加冗余检查。 重新启动文件服务器后,通过查找日志中的最后一个有效记录来恢复文件系统,然后将日志中的记录重播到磁盘文件系统。 在到达任何具有不良冗余检查的记录之后,重播将在最后一次有效记录之前终止。 只有在达到具有不良冗余检查的记录和记录在日志中的位置的最后有效记录之前,如果日志恢复被终止,则在授予客户端对文件系统的访问之前,对文件系统执行“fsck” 表示该冗余校验错误的记录不能与最后一个有效记录并发写入日志。