Re: unable to stat
I remember this in 2.4.4 as a vm bug that trashed my ext2 fs. Mount that
partition readonly and e2fsck it. More than likely the file is probably
being reported as some insane size like ~14 GB. Upgrade to 2.4.7+ as soon
as possible, then repair your fs.
---
Dan Chen crimsun@email.unc.edu
GPG key: www.cs.unc.edu/~chenda/pubkey.gpg.asc
On Sat, 11 Aug 2001, harsha wrote:
> hi,
> recenlty my system went haywire and had to run fsck when i did some
> clearing and fixing of wrong values. among them was
> /usr/share/man/man1/uuidgen.1.gz.
>
> I thought that the problem was solved, but when I ran apt-get update &&
> apt-get update. I came across this problem.
>
> dpkg: error processing /var/cache/apt/archives/e2fsprogs_1.22-2_i386.deb (--unpack):
> unable to stat `./usr/share/man/man1/uuidgen.1.gz' (which I was about to install): Value too large for defined data type
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
> Errors were encountered while processing:
> /var/cache/apt/archives/e2fsprogs_1.22-2_i386.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Hmmn is this a filesystem error or the package is corrupt? I did a
> search on google. The reference where to some large file as much as 2Gb
> gettting tarred or untarred.
Reply to: