Bug 17771 - locate sometimes considers valid database as corrupted
Summary: locate sometimes considers valid database as corrupted
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: slocate (show other bugs)
Version: unstable
Hardware: all Linux
: P2 normal
Assignee: Dmitry V. Levin
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-03 16:46 MSK by Evgenii Terechkov
Modified: 2008-11-05 15:19 MSK (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Evgenii Terechkov 2008-11-03 16:46:34 MSK 
evg@evg ~ $ rpm -q slocate 
slocate-0.2.15-alt1

Какое-то время назад locate -ie всегда стал выдавать:

evg@evg ~ $ locate -ie /struct.h
locate: /var/lib/locate/locatedb: corrupted database

Зашёл под рутом, руками запустил updatedb - никакой реакций.
Comment 1 Dmitry V. Levin 2008-11-04 18:35:54 MSK 
This is /usr/bin/locate regression in slocate-0.2.15-alt1.
Comment 2 Dmitry V. Levin 2008-11-04 18:39:56 MSK 
Reproducer:
$ rm dir -rf && mkdir dir dir/foo dir/0 dir/0/`printf %0127d 1` dir/0/`printf %0127d 2` && /usr/sbin/mklocatedb --searchpaths dir --output db && slocate -d db foo
slocate: db: corrupted database
$ slocate.old -d db foo
dir/foo
Comment 3 Dmitry V. Levin 2008-11-04 20:20:05 MSK 
Fixed in 0.2.16.
Comment 4 Evgenii Terechkov 2008-11-05 15:19:12 MSK 
Туда и дорога.