Unusually large directory - 2.0 peta bytes

[Peter Jeremy]

On 2008-Jun-14 07:17:56 +0200, Goran Lowkrantz <goran.lowkrantz at ismobile.com> wrote:
>drwxr-xr-x   2 root  wheel  2251799813685760 Jun 14 04:06 .

This is 0x8000000000200

># od -c /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO | more
>0000000    s 313   O  \0  \f  \0 004 001   .  \0  \0  \0   1 313   O  \0
>0000020  364 001 004 002   .   .  \0  \0   t 313   O  \0 024  \0  \b  \t
>0000040    P   e   r   l   I   O   .   s   o  \0 217 300   u 313   O  \0
>0000060  324 001  \b  \t   P   e   r   l   I   O   .   b   s  \0 217 300
>0000100   \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
>*
>0001000   \0  \0  \0  \0  \0 002  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
...
>This does not look like a directory, it looks like a shared library, 
>PerlIO.so, that somehow got the directory bit set.

Actually, no.  It looks like a valid directory that somehow managed
to get the high bit in its length set (random bit flip).  The od output
makes it look like it contains (or used to contain) PerlIO.so and
PerlIO.bs.

>Second, how do I remove the directory bit so I can delete the file?

I'd try a fsck - that may detect the inconsistency and fix it to the
point where rm works.  If not, then you'll need to use fsdb(8) - just
be careful with the latter - you can do major damage with it.

Your second issue is how you got a random bit-flip - you might like
to check your hardware.

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080614/45b8e699/attachment.pgp