nate wrote:
>
> Erik Steffl said:
> > system: debian unstable, kernel 2.4.10
> >
> > my /home filesystem was suddenly read-only, here' what I've found:
>
> > I mounted the filesystem, restarted xdm and everything looks ok...
> > any
> > ideas on what's going on?
>
> while i can't speak for 2.4.10 but 2.2 will remount a filesystem
> readonly to prevent damage automatically if there is severe
> disk errors. ive had it do it several times on disks that
> were failing. although everytime it would say something in
> the kernel log
>
> "something something errors, remounting readonly"
there was something like that (right in the beginning of my email):
Nov 15 23:38:04 localhost kernel: EXT2-fs error (device ide0(3,71)):
ext2_new_block: Free blocks count corrupted for block group 120
Nov 15 23:38:04 localhost kernel: Remounting filesystem read-only
at the same time I had problems with memory (full, some processes were
killed):
Nov 15 23:39:14 localhost squid[16292]: Squid Parent: child process
16295 exited due to signal 9
Nov 15 23:39:08 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c0127d7e
Nov 15 23:39:21 localhost kernel: VM: killing process mozilla-bin
Nov 15 23:39:21 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c0127d7e
Nov 15 23:39:21 localhost kernel: VM: killing process nmbd
...etc, few more were killed: squid, xmms, smbd
the problem is I don't know what it means. fsck later on said:
Pass 5: Checking block summary information
Block bitmap differences: -3937687
(that was the only error)
again, I have no idea what that error means (I checked google, found
some posts mentioning it but didn't find anything that would help me to
figure out what's going on). I am mainly interested whether this is a
filesystem problem (software) or disk problem (hardware).
TIA
erik
