Paul Harris wrote:
>
> hi,
>
> the problem with my evil crt1.o file that was hosed in a 'previous
> episode' from a bad filesystem crash through power cut via microsoft
> button (locked console and no chance to telnet for hours), and is still
> not fixed. just got some time to try again, so this time i'm trying
> debugfs. this is a stat of the file:
>
> debugfs: stat crt1.o
> Inode: 272446 Type: character special Mode: 0040 Flags: 0x20202030
> Version: 0
> User: 12320 Group: 8224 Size: 538976288
> File ACL: 0 Directory ACL: 0
> Links: 1 Blockcount: 538976288
> Fragment: Address: 0 Number: 0 Size: 0
> ctime: 0x20202020 -- Fri Jan 30 11:38:08 1987
> atime: 0x30202020 -- Thu Aug 3 09:02:24 1995
> mtime: 0x20202030 -- Fri Jan 30 11:38:24 1987
> BLOCKS:
> 538976304 538976288 807411744 10
> TOTAL: 4
>
> My biggest worry is the size: i only have 6 gig drive, not a 539 gig! what
> do i do to get rid of this file without destroying my system? who are the
> experts on this stuff? I don't want to email Theodore Ts'o if he isn't
> still involved...
>
> hope someone knows...
> Paul
--------------------------------------------------
I did not see this earlier so you may have already answered this. Do you
know what the file is? Looks like it might be a core dump. Can you move
it around or alter its permissions or rename it?
--
John Foster
AdVance-Computing Systems
[EMAIL PROTECTED]
