[regarding chronic filesystem errors]
About the only additional thing I can suggest is upgrading your kernel
(we are now at 2.0.13, I think) and watching to see if the problem goes
away.
Bruce
On Fri, 23 Aug 1996, Luca Maranzano wrote:
> Bruce Perens wrote:
>
> > > I've tryed to e2fsck /dev/hdc2 (thinking that device 16:02 corresponds
> > > to /dev/hdc2) and it found a lot of errors, but it seemed that e2fsck
> > > was able to correct them all; after rebooting similar messages appeared
Bruce Perens wrote:
> > I've tryed to e2fsck /dev/hdc2 (thinking that device 16:02 corresponds
> > to /dev/hdc2) and it found a lot of errors, but it seemed that e2fsck
> > was able to correct them all; after rebooting similar messages appeared
> > again after some hours.
>
> > Any clue about thi
> The first question is this: which device are 16:02 and 16:01 ?
> I looked in /dev searching for devices whith major number 16 but
> I didn't found any. Shouldn't hda and hdc correspond to major 3 and 22 ?
The message is in hex (which is probably a mistake). It's hdc2 and hdc1.
> I've tryed to e
Hi all,
I'm happily running Debian 1.1 with Kernel 2.0.10 on several different
machines here, but last week one of these began to show these messages (after
a crash due to a power failure):
EXT2-fs warning (device 16:01): ext2_free_inode: bit already cleared for inode
24481
EXT2-fs warning (dev
5 matches
Mail list logo
