debian >
debian >What could have caused this I/O error anyway?
almost anything, if the system crashed, or had some bad physical sectors
on it ..or a program crashed while it was writing to disk may of curropted
some stuff..hard to tell. you can always avoid a reboot and you can
always (i believe)
> you try running a e2fsck on it ?
Yes, but it was /home which was always busy, although I stoped every
process I could think of using files in /home. Isn't there a tool to
check which process is using a certain part of the filesystem?
> run e2fsck -c too, i think that is the option to check for
you try running a e2fsck on it ?
run e2fsck -c too, i think that is the option to check for bad blocks. if
its on the root partition you'll have to bring the box down, fastest way
is to init 1, mount -o remount,ro / and run e2fsck on it then mount -o
remount,rw / and init 2 to get back to normal
3 matches
Mail list logo
