[Lustre-discuss] Lost Files - How to remove from MDT

Charles Taylor taylor at hpc.ufl.edu
Mon Apr 19 05:03:21 PDT 2010


On Apr 18, 2010, at 1:14 PM, Andreas Dilger wrote:

> On 2010-04-18, at 07:16, Charles Taylor wrote:
>> On Apr 18, 2010, at 9:35 AM, Miguel Afonso Oliveira wrote:
>>> You are going to have to use "unlink" with something like this:
>>> 
>>> for file in lost_files
>>> 	unlink $file
>> 
>> Nope.   That's really no different than "rm" and produces the same result...
>> 
>> unlink /scratch/crn/bwang/NCS/1O5P/1o5p_wat.prmtop
>> unlink: cannot unlink `/scratch/crn/bwang/NCS/1O5P/1o5p_wat.prmtop': Invalid argument
> 
> This surprises me that "unlink" doesn't work, since that is the answer I was going to give also.  Did you also verify that after this message is posted, that the file isn't actually unlinked?  I suspect that the file name was unlinked, but an error is returned from destroying the OST object, but that is fine since the OST is dead and gone anyway.

Nope.  They are still there following the Invalid argument error.  It seems that before we deactivated the OST we could remove the files but got an error message but once the OST was deactivated, we get the error message and the file (err, its metadata) remains.

> 
> What error messages are posted on the console log (dmesg/syslog)?

Lots of the following but there is a find running as well so I don't think it is necessarily from the rm command.

Lustre: 4286:0:(lov_pack.c:67:lov_dump_lmm_v1()) stripe_size 1048576, stripe_count 1
Lustre: 4286:0:(lov_pack.c:76:lov_dump_lmm_v1()) stripe 0 idx 17 subobj 0x0/0x3dbe6b
Lustre: 4286:0:(lov_pack.c:64:lov_dump_lmm_v1()) objid 0x38f59c8, magic 0x0bd10bd0, pattern 0x1
Lustre: 4286:0:(lov_pack.c:67:lov_dump_lmm_v1()) stripe_size 1048576, stripe_count 1
Lustre: 4286:0:(lov_pack.c:76:lov_dump_lmm_v1()) stripe 0 idx 17 subobj 0x0/0x3dc0fa


Charlie 





More information about the lustre-discuss mailing list