I totally agree we should fix the core cause. If there's anything to prevent file system errors from ever happening, go for it. However, when the inevitable<br>Filesystem errors, Fix(y/n):<br>appears, when was the last time you pressed "n"! Unless you're Theodore tso there's not so much you could do, eh! So why not make that the default<br>
<br><div class="gmail_quote">On Tue, Jun 10, 2008 at 4:36 PM, Eric Sandeen <<a href="mailto:sandeen@redhat.com">sandeen@redhat.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">Ahmed Kamal wrote:<br>
> I would like to propose<br>
><br>
> echo AUTOFSCK_DEF_CHECK=yes >> /etc/sysconfig/autofsck<br>
> echo 'AUTOFSCK_OPT="-y"' >> /etc/sysconfig/autofsck<br>
><br>
> Working with a local ISP in some rural area where there's a lot of power<br>
> cuts! The ISP guys were asking like, "Why is it that Linux boxes need<br>
> manual intervention to get back up after a power cut!" .. "Can't you<br>
> script what you're doing to get it back up" ?!<br>
> Does not having this as the default makes sense in some tangible number<br>
> of cases ?!<br>
><br>
<br>
</div></div>Adding -y could potentially be dangerous. e2fsck asks when the answer<br>
isn't obvious. In some situations, perhaps, but I probably would not<br>
make this default.<br>
<br>
I'm more concerned that you're seeing so many problems; with a<br>
journaling filesystem you really shouldn't have any filesystem metadata<br>
integrity problems on power loss; that is, if you have barriers on<br>
(which ext3 doesn't by default) and if your storage can pass barriers<br>
(which lvm doesn't), or if you have drive write cache disabled (which<br>
hurts performance pretty badly).<br>
<br>
I'd rather address the root of the problem and sort out why, if you are<br>
paying the journaling overhead penalty at runtime, it's not saving you<br>
on power loss.<br>
<br>
-Eric<br>
<font color="#888888"><br>
--<br>
fedora-devel-list mailing list<br>
<a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list" target="_blank">https://www.redhat.com/mailman/listinfo/fedora-devel-list</a><br>
</font></blockquote></div><br>