xfs
[Top] [All Lists]

Re: XFS bug with ftruncate, mmap and holes.

To: linux-xfs@xxxxxxxxxxx
Subject: Re: XFS bug with ftruncate, mmap and holes.
From: Arto Jantunen <viiru@xxxxxxxxxx>
Date: 28 Jan 2002 16:47:58 +0200
In-reply-to: <20020128050623.N14742@xxxxxxxxxxxxxxx>
References: <3C554DF5.80701@xxxxxxx> <6928.1012224206@xxxxxxxxxxxxxxxxxxxxx> <20020128050623.N14742@xxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
Ethan Benson <erbenson@xxxxxxxxxx> writes:
> this sounds as if it could be related to a obscure problem ive been
> observing in apt-get since 2.4.17 (more so with the Dec 23 cvs patch,
> and less so with both split patches). 
> 
> apt-get starts segfaulting on all operations when it reads
> /var/cache/apt/pkgcache.bin and cannot be used until this file is
> removed and apt-get update is rerun, then it will function properly,
> until it happens all over again.  
> 
> someone i was talking to recently has been using the 2.4.17 xfs
> patches with 2.4.18pre kernels and found apt-get failed due to errors
> returned by msync() (which appears to be returning 1 (not -1)).
> msync is involved in writing these apt binary cache files.  
> 
> i have also had apt function fine for some time, then all of the
> sudden start segfaulting, even when no operation which rewrites the
> cache file was run for quite some time, this seems quite consistent
> with the above description.  i haven't reported this yet since its
> been so inconclusive and difficult to reproduce as to not be a very
> helpful bug report.

Happens for me, too. Begun when I first updated to 2.4.17-xfs from
2.4.16-xfs. I have not reported this either, because I can't reproduce
it reliably.

-- 
Arto Jantunen


<Prev in Thread] Current Thread [Next in Thread>