search for: inode_map

Displaying 5 results from an estimated 5 matches for "inode_map".

Did you mean: node_map
2007 Sep 23
0
A preliminary design for an external DB for rsync
...et the new disk get an auto-generated disk_id (even if it ends up with the same devno as the just-unmounted disk had before). We might also want an option to not allow auto-generated disk_ids, to avoid a mount race condition (having the DB routines sleep and lookup the devno again). ----- TABLE: inode_map disk_id int32 ino int64 size int64 mtime int64 ctime int64 md4 byte(16) NULL-OK md5 byte(16) NULL-OK PRIMARY KEY: disk_id + ino (unique) KEY: size + md4 (non-unique) KEY: size + md5 (non-unique) KEY: size + mtime (non-unique) This table facilitates the caching of extra info by inode. It ca...
2019 Sep 11
0
[PATCH v5 0/4] virtio-fs: shared file system for virtual machines
...not easily possible to bring back the state held in memory after the device has been reset. The following areas of the FUSE protocol are stateful and need special attention: * FUSE_INIT - this is pretty easy, we must re-negotiate the same settings as before. * FUSE_LOOKUP -> fuse_inode (inode_map) The session contains a set of inode numbers that have been looked up using FUSE_LOOKUP. They are ephemeral in the current virtiofsd implementation and vary across device reset. Therefore we are unable to restore the same inode numbers upon restore. The solution is persistent ino...
2019 Sep 12
0
[PATCH v5 0/4] virtio-fs: shared file system for virtual machines
...has been reset. > > > > The following areas of the FUSE protocol are stateful and need special > > attention: > > > > * FUSE_INIT - this is pretty easy, we must re-negotiate the same > > settings as before. > > > > * FUSE_LOOKUP -> fuse_inode (inode_map) > > > > The session contains a set of inode numbers that have been looked up > > using FUSE_LOOKUP. They are ephemeral in the current virtiofsd > > implementation and vary across device reset. Therefore we are unable > > to restore the same inode numbers...
2014 Dec 24
14
[PATCH 0/8] extlinux: support unmounted ext2/3/4 filesystem
Hello syslinux, Merry Christmas! These patches will make extlinux work with umounted ext2/3/4 filesystem, for example: $ extlinux -i /dev/sdXN or $ extlinux -i file_block Also it can work with something like: $ extlinux /dev/sdXN --reset-adv or $ extlinux file_block --reset-adv We don't use a new option (I planed to use "-d" but it is already in use), it will check whether the
2015 Jan 02
13
[PATCH 0/9] linux/syslinux: support ext2/3/4 device
Hello, Happy New Year! These patches make syslinux/linux support ext2/3/4, and it doesn't require the root privilege, I'd like to add a separate e2fs/syslinux, if that is more appropriate, it should be easy to do that. I put these patches on github so that you can easily get them in case you'd like to test them. (The repo's name is sys_tmp, which avoids confusing others, I will