Date: Tue, 15 Jul 2008 09:36:00 -0700 From: "Steve Franks" <stevefranks@ieee.org> To: "Wojciech Puchar" <wojtek@wojtek.tensor.gdynia.pl> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: OT-ish: fedora->crash->single user fsck; FreeBSD->crash->smooth recovery Message-ID: <539c60b90807150936x458a41c6xe0f9d1a4b71ad116@mail.gmail.com> In-Reply-To: <20080715072456.T1638@wojtek.tensor.gdynia.pl> References: <539c60b90807142030u506394e7jdcdedd965ec16706@mail.gmail.com> <20080715072456.T1638@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Ok, I'll quit ranting and actually ask a question: The real big thing >> that suprised me (about Fedora), is that every damn time it crashes, I >> have to sit through 20 minutes of fsck when it boots, then it cries, >> gags, and throws me into a root console to run fsck again, manually, >> for 20 more minutes. I'm thinking about symlinking fsck to a rather >> dirtier word on the Fedora box. > > yes it is normal. > > linux filesystem works like in -o async mode, is just caches what it have to > write and write whenever it likes at whatever sequence. > > in linux it is always presented as feature not bug. > > > another very stupid thing is TOO delayed writes, i mean linux simply caches > things as long as there are free memory then just starts lots of writes at > once efectively halting the system for a while. > Ok, so you are saying the write caching is radically different on FreeBSD than what I know of Win/Lin? Or is the timeout to flush just some really small period like 100mS? Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539c60b90807150936x458a41c6xe0f9d1a4b71ad116>