Date: Fri, 18 May 2007 22:58:26 -0700 (PDT) From: Gore Jarold <gore_jarold@yahoo.com> To: freebsd-fs@freebsd.org Subject: dangers of delaying an fsck on busy fileserver ? Message-ID: <550589.3257.qm@web63006.mail.re1.yahoo.com>
next in thread | raw e-mail | index | archive | help
I have a busy fileserver - 5-20 sftp/rsync processes running on it at all times. For unknown reasons, this server crashes in the middle of the night sometimes. When it does, I comment out my four big arrays in /etc/fstab, reboot, and fsck them manually (without a snapshot and BG fsck). Easy. The problem is, I need to sit around and wait for an fsck in the middle of the night and then re-edit fstab and reboot. So I am curious ... what happens if I instruct the NOC tech to just press the reset switch instead of calling me ? If he does this, the system will boot, the arrays will come online, and since I have a very very long time set until bg_fsck starts, I can then reboot the machine and foreground fsck it during sunlight hours. But it does mean that users will continue to operate on those dirty disks for 4-8 hours until I do that. Is this a dangerous strategy ? Does this put me at some increased risk of finding myself with disks that cannot be fsck'd ? (I've never seen it, but I have heard horror stories...) Will I lose a lot of the data that has been transacted during the hours that the disks were used in a dirty state ? Any comments ? ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?550589.3257.qm>