From mint-bounce@lists.fishpool.fi Fri Sep 30 22:49:42 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] file system check From: Evan Langlois To: josephus , mint@fishpool.com In-Reply-To: <433D804A.7070204@earthlink.net> References: <924346361.20050930001725@der-ingo.de> <433D804A.7070204@earthlink.net> Content-Type: text/plain Date: Fri, 30 Sep 2005 15:48:46 -0500 Message-Id: <1128113326.736.7.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - esc14.midphase.com X-AntiAbuse: Original Domain - fishpool.com X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - coolrunningconcepts.com X-Source: X-Source-Args: X-Source-Dir: X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: evan@coolrunningconcepts.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=0.5 tagged_above=-50.5 required=7.0 tests=BAYES_00, RCVD_NUMERIC_HELO X-Spam-Level: On Fri, 2005-09-30 at 13:13 -0500, josephus wrote: > I have a 160 mxxtor disk running Linux. The only problem is this > mechanism. The disk requires a 8meg cache hit. As a result I cannot > ever boot a clean disk. My system boots and generally works. but I > cannot boot RO, the system will NEVER boot, it just reboots. E2FSCK > will reports strange errors in the FILE SYSTEM> Sync will not flush > this giant buffer. > > So folks running large disks need to know that the on disk cache is much > larger than any sync will process. If you think this is normal behavior you really need to hit yourself over the head a few times with a brick until you knock some sense into yourself. Linux is quite happy with terabytes of storage and it most often, all drives have a cache. The sync call doesn't care how big your hardware drive caches are. Once a drive is unmounted, the file system is guaranteed to be clean and will come back up clean, no matter how big the cache. I suggest you format the drive and start over. Since you aren't using journaling, either you NEVER power off your system without shutting down and always run fsck at boot (multiple times if it finds an error) or start using a journaled filesystem (ext2 converts to ext3 instantly). If you continue to have problems, throw the drive away. Its faulty. To say that Linux can't handle a drive because it has an 8MB cache is absurd. Most drives you buy today have 8MB or more of cache. Please don't spread misinformation!! -- Evan