lkml.org 
[lkml]   [1998]   [May]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: FW: Corrupted filesystem
Date
Followup to:  <Pine.LNX.3.96.980520151125.162F-100000@ppp3.csudh.edu>
By author: Trevor Johnson <trevor@jpj.net>
In newsgroup: linux.dev.kernel
>
> > We experienced a system crash and the fsck upon reboot failed with
> > the following message:
> >
> > Directory Inode 5, block 0, offset 0: directory corrupted
> > Salvage <y>?
>
> By default, Linux uses write caching, meaning that data and directory
> information isn't written immediately to disk. If you run /sbin/update,
> then that information will be written out periodically. If you use the
> "sync" option to mount (this is the default in *BSD), then the write
> caching will be disabled. This can be much slower, but if your system
> crashes, or you have users accustomed to DOS who abruptly power it off,
> there will be minimal loss of data.
>

Inode 5 is a reserved inode; something far more sinister is going on
here.

-hpa
--
PGP: 2047/2A960705 BA 03 D3 2C 14 A8 A8 BD 1E DF FE 69 EE 35 BD 74
See http://www.zytor.com/~hpa/ for web page and full PGP public key
I am Bahá'í -- ask me about it or see http://www.bahai.org/
"To love another person is to see the face of God." -- Les Misérables

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.043 / U:1.564 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site