Changes between Version 8 and Version 9 of manuals/AdvidoryDelete


Ignore:
Timestamp:
08/03/07 15:22:52 (14 years ago)
Author:
patrick
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • manuals/AdvidoryDelete

    v8 v9  
    1818 
    1919 === Solution ===  
    20  
    21    We hope to get this fixed as soon as possible. 
    22  
    23 ---- 
    24  
    25  == Triggered by a issue with pnfs == 
    26  
    27  === Symptom === 
    28  
    29      srm-advisory-delete or lcg-del report a problem and the file is indeed still in the pnfs filesystem. Very often, this affects only 
    30      a particular subtree of pnfs but not whle system. 
    31  
    32  === Details === 
    33  
    34     The advisory delete command needs a function of the pnfs filesystem to obtain the filepath by the pnfs i-node (pnfsID). For still 
    35     unknown reasons, it happens that for a particular subset of the pnfs tree the function doesn't work, due a piece of information 
    36     lots in one of the pnfs database. A good indication that this happened is to run the pnfs pathfinder command on a pnfs id which 
    37     exists, but for which the delete didn't work. You will very likely get something similiar to this  
    38     {{{ 
    39 MY_COMPUTER $ cd /pnfs/fs 
    40 MY_COMPUTER $ PATH=/opt/pnfs/tools:$PATH 
    41 MY_COMPUTER $ pathfinder 00010000000000000000A2C8 
    42 00010000000000000000A2C8 generated 
    43 0001000000000000000040A8 hone 
    44 000100000000000000001060 - 
    45 000100000000000000001040 fs 
    46 000100000000000000001020 root 
    47 000100000000000000001000 - 
    48 000000000000000000000100 - 
    49 000000000000000000000000 - 
    50 /root/fs/hone/generated 
    51     }}} 
    52     This is the line which is obviously not correct  
    53     {{{ 
    54 000100000000000000001060 - 
    55     }}} 
    56  
    57  === How to fix this === 
    58  
    59    Open a ticket at support@dCache.org and send the result of the script below. 
    60  
    61 {{{ 
    6220 
    6321   We hope to get this fixed as soon as possible.