I am using the e2fsprogs-1.12-WIP here . All seems well.
Just one minor cavaet, When using 'e2fsck -fy /dev/?d??'
an (relatively) small filesystem IE: I have a system with
192MB Memory and it -never- accessed the disk drive .
umount /mnt
e2fsck -fy /dev/sdxx < which repaired some errors
e2fsck -fy /dev/sdxx < which never re-read the disk ????
mount /dev/sdxx /mnt
did somethnig on the disk
umount /mnt
e2fsck -fy /dev/sdxx < which re-read the disk
e2fsck -fy /dev/sdxx < which never re-read the disk ????
After .sig is all the info I can gater about the system
I am refering too. I hope this is enough to go on.
I beleive that the OS is caching the information that
e2fsck is requesting & thus it never gets to re-read the
disk .
Yes, and yes. There's nothing wrong with this, though. The OS was
doing what it was supposed to be doing --- speeding up disk accesses by
using your spare memory (with 192 MB, you have a lot of spare memory :-)
as buffer cache. Was there some reason you thought enough of this to
comment on it?
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu