>> I agree that it would be very nice for fsck to have some kind of
>> logging mechanism.
> The problem of where to store the log files is actually an interesting
> one. The log file you most badly want to have is the one after the
> catastrophic fsck run, but at that point you might not want to mount the
> filesystem read/write. So, even if you a standard rc script which
> stores the log file in RAM disk and then copies the log file from the
> RAM disk to the disk after the filesystem is mounted read/write, that
> might not necessarily be the right thing.
> So I've been thinking that one of the options might be to store the
> binary log file on a floppy disk, and that might be the approach that's
> used when running e2fsck from a rescue disk.
> Another design question is how many log files to save? A user might
> reboot the system several times while trying to fix a mysterious system
> problem, and so simply saving the last 2 or 3 log files isn't
> necessarily the right answer either.
>
> So this is actually an interesting problem, and getting the design right
> so that it works for mere mortals, and not just kernel weanies has some
> subtle points that have to be gotten right.
Sounds like it might be an idea to reserve part of a specified swap
partition for this purpose - but that would need some serious tweaking
to the mm subsystem to get right, so probably shouldn't be considered
as more than a wild idea at a brainstorming session...
Best wishes from Riley.
--- * ftp://ps.cus.umist.ac.uk/pub/rhw/Linux * http://ps.cus.umist.ac.uk/~rhw/kernel.versions.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/