On 27-Jan-99, Nathan E Norman took time to write :
> I'm flying by the seat of my pants here, but I believe it has something
> to do with a daemon's log file not being completely cleared before the
> system shuts down (as in `shutdown -h now').
probably.
> I was told that the "deleted inode has
On Tue, 26 Jan 1999, Hamish Moffatt wrote:
: On Tue, Jan 26, 1999 at 01:42:25PM +0100, E.L. Meijer Eric" wrote:
: > >
: > > This is an unusual checking by my machine (this is all I could
cut&paste),
: > > has anything gone wrong here?
: >
: > [ output of regular fsck check ]
: >
: > Th
> >
> > In a message dated 1/26/99 6:25:42 AM Central Standard Time,
> > [EMAIL PROTECTED] writes:
> >
> > > This is an unusual checking by my machine (this is all I could cut&paste),
> > > has anything gone wrong here?
> > >
> > >
> > > /dev/hda2 has reached maximal mount count, check forc
>
> In a message dated 1/26/99 6:25:42 AM Central Standard Time,
> [EMAIL PROTECTED] writes:
>
> > This is an unusual checking by my machine (this is all I could cut&paste),
> > has anything gone wrong here?
> >
> >
> > /dev/hda2 has reached maximal mount count, check forced.
> > Pass 1: C
In a message dated 1/26/99 6:25:42 AM Central Standard Time,
[EMAIL PROTECTED] writes:
> This is an unusual checking by my machine (this is all I could cut&paste),
> has anything gone wrong here?
>
>
> /dev/hda2 has reached maximal mount count, check forced.
> Pass 1: Checking inodes, block
"E.L. Meijer \(Eric\)" <[EMAIL PROTECTED]> writes:
> If there are any `lost files', they will be put in the `lost+found'
> directory on the disk.
In this case it looks as if some file (at inode 33194, spanning the
blocks 134439--134447) was a little more more lost than usually,
since the inode ha
On Tue, Jan 26, 1999 at 01:42:25PM +0100, E.L. Meijer Eric" wrote:
> >
> > This is an unusual checking by my machine (this is all I could cut&paste),
> > has anything gone wrong here?
>
> [ output of regular fsck check ]
>
> This is not a bug, it is a feature. After a number of reboots, your
>
>
> This is an unusual checking by my machine (this is all I could cut&paste),
> has anything gone wrong here?
[ output of regular fsck check ]
This is not a bug, it is a feature. After a number of reboots, your
hard disks are checked by the fsck program. The same thing happens if
you do not s
This is an unusual checking by my machine (this is all I could cut&paste),
has anything gone wrong here?
/dev/hda2 has reached maximal mount count, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 33194 has zero dtime. Fix? yes
Pass 2: Checking directory structure
Pass 3:
9 matches
Mail list logo