* fsck problem
@ 2002-09-12 14:48 Michael Cuffaro
2002-09-12 15:59 ` rich+ml
0 siblings, 1 reply; 2+ messages in thread
From: Michael Cuffaro @ 2002-09-12 14:48 UTC (permalink / raw)
To: linux-admin
Hi,
Note: I'm not subscribed to the list so please reply
to me personally at Michael.Cuffaro@ericsson.ca
Not very long ago (about a week) my Linux system
crashed. After it came up again I got the message:
"Special (device/socket/fifo) inode 260915 has
non-zero size. FIXED."
Great, I thought. Unfortunately I get the message
every time fsck runs (or rather is forced to run)
after boot. I shutdown using "shutdown -F -r now" and
get the exact same message every time.
I've tried booting with the rescue disk and running
fsck on the filesystem twice in a row. This works
without error, but the next time I boot up the system
normally (with the -F flag) I get the error again.
I'm using fsck 1.27 and the filesystem I'm having
problems with is the root filesystem (ext2).
Any ideas?
thanks,
-Mike
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: fsck problem
2002-09-12 14:48 fsck problem Michael Cuffaro
@ 2002-09-12 15:59 ` rich+ml
0 siblings, 0 replies; 2+ messages in thread
From: rich+ml @ 2002-09-12 15:59 UTC (permalink / raw)
To: Michael Cuffaro; +Cc: linux-admin
FWIW I've seen this on machines with flaky ram. If this is x86 box, try
testing with memtest86, see www.memtest86.com.
== Rich
On Thu, 12 Sep 2002, Michael Cuffaro wrote:
> Date: Thu, 12 Sep 2002 07:48:38 -0700 (PDT)
> From: Michael Cuffaro <m_cuffa@yahoo.com>
> To: linux-admin@vger.kernel.org
> Subject: fsck problem
>
> Hi,
>
> Note: I'm not subscribed to the list so please reply
> to me personally at Michael.Cuffaro@ericsson.ca
>
> Not very long ago (about a week) my Linux system
> crashed. After it came up again I got the message:
> "Special (device/socket/fifo) inode 260915 has
> non-zero size. FIXED."
>
> Great, I thought. Unfortunately I get the message
> every time fsck runs (or rather is forced to run)
> after boot. I shutdown using "shutdown -F -r now" and
> get the exact same message every time.
>
> I've tried booting with the rescue disk and running
> fsck on the filesystem twice in a row. This works
> without error, but the next time I boot up the system
> normally (with the -F flag) I get the error again.
>
> I'm using fsck 1.27 and the filesystem I'm having
> problems with is the root filesystem (ext2).
>
> Any ideas?
>
> thanks,
> -Mike
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-09-12 15:59 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-12 14:48 fsck problem Michael Cuffaro
2002-09-12 15:59 ` rich+ml
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox