Hello,
Unfortunately we currently have a data center provider which suffer power outages regularly. We realize that the first solution is to switch to a better data center that has no such problems. We are looking at options but at this point we have to solve it before we move to another place.
We have Fedora v14 with ext3. Also we have FreeBSD v8.1 with UFS. The point is that when there are blackouts the only server that has problems is the FreeBSD v8.1. In large percentage I have to boot into single user mode and run fsck to repair the file system. This does not happen with Fedora servers.
Questions
* Why FreeBSD v8.1 with UFS is easily corrupted? In a power outage is certain to fail to boot the file system, this does not happen with Fedora v9 or v14 with ext3.
* Is there something misconfigured on the FreeBSD server that we have?
* Is there any way to prevent this from happening? maybe using FreeBSD v9 with ZFS or UFS Journaled?
Conclusion
When booting I've chosen single user mode and executed "fsck -y" to fix the issue. Is this the right way or exists another one?
One guy recommend me to put the following code in rc.conf to solve the issue.
Is the code above solve the problem?
Regards,
Gerardo
Unfortunately we currently have a data center provider which suffer power outages regularly. We realize that the first solution is to switch to a better data center that has no such problems. We are looking at options but at this point we have to solve it before we move to another place.
We have Fedora v14 with ext3. Also we have FreeBSD v8.1 with UFS. The point is that when there are blackouts the only server that has problems is the FreeBSD v8.1. In large percentage I have to boot into single user mode and run fsck to repair the file system. This does not happen with Fedora servers.
Questions
* Why FreeBSD v8.1 with UFS is easily corrupted? In a power outage is certain to fail to boot the file system, this does not happen with Fedora v9 or v14 with ext3.
* Is there something misconfigured on the FreeBSD server that we have?
* Is there any way to prevent this from happening? maybe using FreeBSD v9 with ZFS or UFS Journaled?
Conclusion
When booting I've chosen single user mode and executed "fsck -y" to fix the issue. Is this the right way or exists another one?
One guy recommend me to put the following code in rc.conf to solve the issue.
Code:
fsck_y_enable="YES"
background_fsck="NO"
Is the code above solve the problem?
Regards,
Gerardo