On Wednesday 26 July 2006 02:03, Dan Nelson wrote:
In the last episode (Jul 25), Michael P. Soulier said:
A while ago there was a power failure in my house, long enough to
wear down the UPS. I had to power-on my server when I got home
(crappy bios), and I noticed after I logged-in that fsck
A while ago there was a power failure in my house, long enough to wear down
the UPS. I had to power-on my server when I got home (crappy bios), and I
noticed after I logged-in that fsck was running non-interactively in the
background.
Question: If it finds problems that require administrator
In the last episode (Jul 25), Michael P. Soulier said:
A while ago there was a power failure in my house, long enough to
wear down the UPS. I had to power-on my server when I got home
(crappy bios), and I noticed after I logged-in that fsck was running
non-interactively in the background.
On 25/07/06 Dan Nelson said:
It logs an error to syslog, and the next time you reboot it forces a
foreground check so it can prompt you for instructions.
Ah. I'd better look for that then. :)
You should be using ext3 on Linux :)
Been there, done that, experienced the file corruption. It
