Mailing List Archive: Error in function kino_FSFolder_delete

Error in function kino_FSFolder_delete_file

Sep 4, 2007, 2:17 AM

Post #1 of 6 (2260 views)

Hello Marvin,

You're probably aware of this error in the current subversion:

Error in function kino_FSFolder_delete_file at
../c_src/KinoSearch/Store/FSFolder.c:164: Couldn't remove file
'/usr/share/locale/en_US/LC_MESSAGES/libc.mo': No such file or directory
at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/InvIndex.pm
line 58
KinoSearch::InvIndex::__ANON__() called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Store/Lock.pm
line 35
eval {...} called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Store/Lock.pm
line 32
KinoSearch::Store::Lock::run_while_locked('KinoSearch::Store::Lock=SCALAR(0x8b76cf8)',
'do_body', 'CODE(0x8b76c14)') called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/InvIndex.pm
line 65
KinoSearch::InvIndex::clobber('KinoSearch::InvIndex', 'schema',
'Test::Schema=SCALAR(0x8b206d8)', 'folder',
'/path/www.testsite.com.site_index') called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Schema.pm
line 50
KinoSearch::Schema::clobber('Test::Schema',
'path/www.testsite.com.site_index') called at
/etc/test/indexer/indexer line 136
at /usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Store/Lock.pm
line 39
KinoSearch::Store::Lock::run_while_locked('KinoSearch::Store::Lock=SCALAR(0x8b76cf8)',
'do_body', 'CODE(0x8b76c14)') called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/InvIndex.pm
line 65
KinoSearch::InvIndex::clobber('KinoSearch::InvIndex', 'schema',
'Test::Schema=SCALAR(0x8b206d8)', 'folder',
'path/www.testsite.com.site_index') called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Schema.pm
line 50
KinoSearch::Schema::clobber('Test::Schema',
'path/www.testsite.com.site_index') called at
/etc/test/indexer/indexer line 136

OR:

Error in function kino_FSFolder_delete_file at
../c_src/KinoSearch/Store/FSFolder.c:164: Couldn't remove file '0': No
such file or directory
at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/InvIndex.pm
line 58
KinoSearch::InvIndex::__ANON__() called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Store/Lock.pm
line 35
eval {...} called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Store/Lock.pm
line 32

...

I'll revert back to a previous version and let you know.

regards
Henry

_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch

Re: Error in function kino_FSFolder_delete_file [ In reply to ]

henka at cityweb

Sep 4, 2007, 9:19 AM

Post #2 of 6 (2148 views)

Permalink

reverted to 2503 and I could be wrong since I didn't let it run all day,
but the previous error did not appear again, except I got the following
occasional lock error (and I know I'm not trying to index something which
is already being indexed):

Failed to obtain lock at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Store/Lock.pm line 34
eval {...} called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Store/Lock.pm line 32
KinoSearch::Store::Lock::run_while_locked('KinoSearch::Store::Lock=SCALAR(0x8b76e18)',
'do_body', 'CODE(0x8b76d34)') called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/InvIndex.pm line 65
KinoSearch::InvIndex::clobber('KinoSearch::InvIndex', 'schema',
'Test::Schema=SCALAR(0x8b20810)', 'folder',
'/path/www.testsite.com.site_index')
called at /usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Schema.pm
line 50
KinoSearch::Schema::clobber('Test::Schema', '/www.testsite.com.site_index')
called at /etc/test/indexer/indexer line 136
at /usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Store/Lock.pm line 39
KinoSearch::Store::Lock::run_while_locked('KinoSearch::Store::Lock=SCALAR(0x8b76e18)',
'do_body',
'CODE(0x8b76d34)') called at
/usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/InvIndex.pm line 65
KinoSearch::InvIndex::clobber('KinoSearch::InvIndex', 'schema',
'Test::Schema=SCALAR(0x8b20810)',
'folder', '/www.testsite.com.site_index')
called at /usr/lib/perl5/site_perl/5.8.7/i486-linux/KinoSearch/Schema.pm
line 50

Will now roll back to revision 2500 and give that a try and let you know.

Regards
Henry

_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch

Re: Error in function kino_FSFolder_delete_file [ In reply to ]

marvin at rectangular

Sep 4, 2007, 9:31 AM

Post #3 of 6 (2145 views)

Permalink

On Sep 4, 2007, at 2:17 AM, Henka wrote:

> You're probably aware of this error in the current subversion:

No, I hadn't been.

> Error in function kino_FSFolder_delete_file at
> ../c_src/KinoSearch/Store/FSFolder.c:164: Couldn't remove file
> '/usr/share/locale/en_US/LC_MESSAGES/libc.mo': No such file or
> directory

> OR:
>
> Error in function kino_FSFolder_delete_file at
> ../c_src/KinoSearch/Store/FSFolder.c:164: Couldn't remove file '0': No
> such file or directory

The error message is messed up. Those aren't the actual files KS is
trying to delete. I used the wrong ByteBuf string pointer; it's
pointing to memory that was freed the line before.

void
FSFolder_delete_file(FSFolder *self, const ByteBuf *filename)
{
ByteBuf *path = full_path(self, filename);
if ( remove(path->ptr) ) {
REFCOUNT_DEC(path);
CONFESS("Couldn't remove file '%s': %s", path->ptr,
strerror(errno));
}
else {
REFCOUNT_DEC(path);
}
}

The message appears to be complete garbage because if it had been
freed-but-still-correct, path->ptr would have started with the
FSFolder object's directory name, which is an absolute path.

I've fixed the error message as of repository revision 2505. I would
be curious to know what the actual files are.

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/

_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch

Re: Error in function kino_FSFolder_delete_file [ In reply to ]

henka at cityweb

Sep 4, 2007, 12:30 PM

Post #4 of 6 (2143 views)

Permalink

> The message appears to be complete garbage because if it had been
> freed-but-still-correct, path->ptr would have started with the
> FSFolder object's directory name, which is an absolute path.
>
> I've fixed the error message as of repository revision 2505. I would
> be curious to know what the actual files are.

Cool, I'll give 2502 a swing and report back when the error is triggered.

Regards
Henry

_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch

Re: Error in function kino_FSFolder_delete_file [ In reply to ]

marvin at rectangular

Sep 4, 2007, 12:34 PM

Post #5 of 6 (2158 views)

Permalink

On Sep 4, 2007, at 12:30 PM, Henry wrote:

>> The message appears to be complete garbage because if it had been
>> freed-but-still-correct, path->ptr would have started with the
>> FSFolder object's directory name, which is an absolute path.
>>
>> I've fixed the error message as of repository revision 2505. I would
>> be curious to know what the actual files are.
>
> Cool, I'll give 2502 a swing and report back when the error is
> triggered.
^

I assume that's a typo.

I recommend 2507. And if you're doing deletions, you're going to
need to rewrite indexes from scratch. The problem Scott reported is
an honest-to-goodness index corruption issue.

Marvin Humphrey
Rectangular Research
http://www.rectangular.com/

_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch

Re: Error in function kino_FSFolder_delete_file [ In reply to ]

henka at cityweb

Sep 4, 2007, 11:16 PM

Post #6 of 6 (2142 views)

Permalink

>
> On Sep 4, 2007, at 12:30 PM, Henry wrote:
>
>>> The message appears to be complete garbage because if it had been
>>> freed-but-still-correct, path->ptr would have started with the
>>> FSFolder object's directory name, which is an absolute path.
>>>
>>> I've fixed the error message as of repository revision 2505. I would
>>> be curious to know what the actual files are.
>>
>> Cool, I'll give 2502 a swing and report back when the error is
>> triggered.
> ^
>
> I assume that's a typo.

ug, yes.

> I recommend 2507. And if you're doing deletions, you're going to
> need to rewrite indexes from scratch. The problem Scott reported is
> an honest-to-goodness index corruption issue.

No problem , will do.

_______________________________________________
KinoSearch mailing list
KinoSearch@rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch