On Mon, May 23, 2016 at 1:36 AM, LEIBOVICI Thomas <[email protected]>
wrote:

> Nathan,
>
> You can check the contents of robinhood DB about this file:
>     rbh-report -e 0x200018285:0xf4:0x0
>
> Also, to help troubleshooting, can you indicate the rbh-find command that
> returns this error?
>
>
Thomas,

The command I ran was:
# rbh-find -f lfs3 -mtime +60 -s +4G -lsost /mnt/lfs3

The rbh-report and lfs fid2path methods both worked quickly (and returned
the same path).  Great!

It seems that there *are* stripes defined in the filesystem, but somehow
Robinhood did not pick them up.  See below for details.  If I had to guess
based on the other files in the same directory, the user was experimenting
with different stripe settings and perhaps interrupted the process.  One of
their scripts has a commented out line that includes "lfs setstripe
fort.63.nc -s 10m -o -1 -c -1".

Probably the file can safely be deleted, but if there is a way to force
Robinhood to reread the stripe information, then I'm happy to try that too.

Thanks,
Nathan


# rbh-report -f lfs3 -e 0x200018285:0xf4:0x0
Using config file '/etc/robinhood.d/tmpfs/lfs3.conf'.
id             : [0x200018285:0xf4:0x0]
2016/05/23 09:06:45 [20313/1] ListMgr | Warning: the number of stripe items
(0) doesn't match stripe count (36)! (Pk='0x200018285:0xf4:0x0')
parent_id      : [0x200018226:0x1f6f8:0x0]
name           : fort.63.nc
path updt      : 2016/05/20 06:37:30
path           : /mnt/lfs3/projects/DIR/test_writing_new/fort.63.nc
depth          : 6
stripe_cnt, stripe_size,      pool:        36,    10.00 MB,
stripes        : (none)
user           : USER
group          : GROUP
size           : 19.54 GB
spc_used       : 19.54 GB
creation       : 2015/07/17 02:51:11
last_access    : 2015/02/12 05:45:30
last_mod       : 2015/02/12 05:45:30
type           : file
mode           : rw-r--r--
nlink          : 1
md updt        : 2016/05/20 06:37:30
invalid        : no

# lfs fid2path /mnt/lfs3 0x200018285:0xf4:0x0
/mnt/lfs3/projects/DIR/test_writing_new/fort.63.nc

# cd /mnt/lfs3/projects/DIR/test_writing_new/
# lfs getstripe fort.63.nc
fort.63.nc
lmm_stripe_count:   36
lmm_stripe_size:    10485760
lmm_pattern:        1
lmm_layout_gen:     0
lmm_stripe_offset:  33
obdidx objid objid group
   33      18245350    0x11666e6             0
   21      18244362    0x116630a             0
   15      18244241    0x1166291             0
    4      18244592    0x11663f0             0
   28      18244247    0x1166297             0
   10      18243910    0x1166146             0
   34      18245678    0x116682e             0
   22      18245318    0x11666c6             0
   16      18244722    0x1166472             0
    5      18241307    0x116571b             0
   29      18246416    0x1166b10             0
   11      18245079    0x11665d7             0
   35      18245774    0x116688e             0
   23      18244712    0x1166468             0
   17      18244954    0x116655a             0
    0      18244582    0x11663e6             0
   24      18247707    0x116701b             0
    6      18244646    0x1166426             0
   30      18245293    0x11666ad             0
   18      18244380    0x116631c             0
   12      18245875    0x11668f3             0
    1      18246116    0x11669e4             0
   25      18246776    0x1166c78             0
    7      18245891    0x1166903             0
   31      18245789    0x116689d             0
   19      18244714    0x116646a             0
   13      18245614    0x11667ee             0
    2      18242264    0x1165ad8             0
   26      18245125    0x1166605             0
    8      18245264    0x1166690             0
   32      18244371    0x1166313             0
   20      18245092    0x11665e4             0
   14      18244715    0x116646b             0
    3      18243844    0x1166104             0
   27      18244727    0x1166477             0
    9      18245496    0x1166778             0



@Colin: a simpler way to determine entry path from its id is
> lfs fid2path <fsname> 0x200018285:0xf4:0x0
>
> Regards,
> Thomas
>
> On 05/23/16 06:54, Colin Faber wrote:
>
> You could try and determine the file by SQL query against ENTRIES and
> NAMES table.
> On May 22, 2016 9:12 PM, "Nathan Dauchy - NOAA Affiliate" <
> [email protected]> wrote:
>
>> Greetings All,
>>
>> Has anyone seen this error from "rbh-find" before, and is there an easy
>> way to figure out what file has the problem?
>>
>> 2016/05/23 02:58:51 [36321/1] ListMgr | Warning: the number of stripe
>> items (0) doesn't match stripe count (36)! (Pk='0x200018285:0xf4:0x0')
>>
>> Thanks,
>> Nathan
>>
>>
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
robinhood-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/robinhood-support

Reply via email to