search for: block_

...the needed information (and not hit the disk at all while iterating through the list of files). What's puzzling me though is the poor performance of this approach (not even near the 26 MB/s mark). Reading the inodes is indeed fast, but reading the directory blocks is not. Using /proc/sys/vm/block_dump logging, I verified that the blocks are read sequentially, with some gaps in between. A typical sequence of reading the directory blocks will look like this: READ block 21249176 on dm-0 READ block 21249184 on dm-0 READ block 21249192 on dm-0 READ block 21249200 on dm-0 REA...

...6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.afr.data01-client-0=0x000000000000000100000000 trusted.gfid=0x7e8513f4d4e24e66b0ba2dbe4c803c54 # getfattr -d -m . -e hex /mnt/AIDATA/data/home/allac/experiments/171023_105655_mini_imagenet_projection_size_mixing_depth_num_filters_filter_size_block_depth_Explore\ architecture\ capacity/Explore\ architecture\ capacity\(projection_size\=32\;mixing_depth\=0\;num_filters\=64\;filter_size\=3\;block_depth\=3\)/model.ckpt-70001.data-00000-of-00001.tempstate1629411508065733704 getfattr: Removing leading '/' from absolute path names # file: mnt...

...h the vHBA was configured. The following example lists the pertinent part of the tree for the example HBA "scsi_host5": +- scsi_host5 | +- scsi_host7 +- scsi_target5_0_0 | | | +- scsi_5_0_0_0 | +- scsi_target5_0_1 | | | +- scsi_5_0_1_0 | +- scsi_target5_0_2 | | | +- scsi_5_0_2_0 | | | +- block_sdb_3600a0b80005adb0b0000ab2d4cae9254 | +- scsi_target5_0_3 | +- scsi_5_0_3_0 The "block_" indicates it's a block device, the "sdb_" is a convention to signify the the short device path of "/dev/sdb", and the short device path or the number can be used to search th...

On 11/16/2017 04:12 PM, Nithya Balachandran wrote: > > > On 15 November 2017 at 19:57, Frederic Harmignies > <frederic.harmignies at elementai.com > <mailto:frederic.harmignies at elementai.com>> wrote: > > Hello, we have 2x files that are missing from one of the bricks. > No idea how to fix this. > > Details: > > # gluster volume

On Sun, 2003-11-16 at 17:13, Chris Lattner wrote: > > The point here is that XPL needs to keep track of what a given variable > > represents at the source level. If the compiler sees a map that is > > initially small it might represent it in LLVM assembly as a vector of > > pairs. Later on, it gets optimized into being a hash table. In order to > > do that and keep

> The point here is that XPL needs to keep track of what a given variable > represents at the source level. If the compiler sees a map that is > initially small it might represent it in LLVM assembly as a vector of > pairs. Later on, it gets optimized into being a hash table. In order to > do that and keep track of things, I need to know that the vector of > pairs is