On Thu, 13 Aug 2009, Guillem Jover wrote: > On Wed, 2009-08-12 at 23:27:05 +0200, Raphael Hertzog wrote: > > On Tue, 11 Aug 2009, Peter Fritzsche wrote: > > > > What removes it? I suspect it's not dpkg... (or we would have noticed it > > > > already) > > > Hm, only started dpkg. So I suspected it. > > > > Did your machine crash/lose power during an upgrade?
More questions: - what kernel version are you using? - what filesystem are you using for /var/lib/dpkg? > > Maybe the bug is a missing fsync() in dpkg in some cases... but currently > > it looks like a filesystem problem yes. > > dpkg does not directly extract the control files, it uses dpkg-deb and > that ones uses tar to extract those files. So either filesystem or tar > related, but very improvable to be dpkg itself. Doesn't dpkg do some renames afterwards? IIRC renames must also be protected by fsync() calls on the directory file descriptor (although that part has been mostly fixed again in recent kernels by new heuristics). Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
