public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Albert Hopkins <marduk@letterboxes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] memory(gray matter) needs jog
Date: Thu, 29 Oct 2009 18:46:02 -0400	[thread overview]
Message-ID: <1256856363.135440.6.camel@centar> (raw)
In-Reply-To: <a0811460910291454i2a6c1bb6m1a1a500bdb33b38d@mail.gmail.com>

On Thu, 2009-10-29 at 15:54 -0600, Maxim Wexler wrote:
> Hi group,
> A while back I needed help with an ext2 file system that required
> checking every boot before mounting. The drive suffered from errors
> involving 'non-contiguous files'

I'm not sure what your problem was but this wasn't it.  "Non-contiguous
files" simply means there is some fragmentation in your filesystem,
which is totally natural.  It's not an error, or even a warning for that
matter. It's informational.  High fragmentation is an indication that
your filesystem may not be performing optimally, but it's not an error.

> .The solution was to run (this is
> where things get hazy) e2fsck <option> <option> on the offender. I
> keep thinking it's '-i -o', but there's no such options. Maybe it
> wasn't e2fsck at all. I can't remember. I don't think it was
> '-f''(force).

I'm not sure why your system needed to be checked for each boot.
Perhaps you can post the exact error message?  I'm pretty sure it wasn't
fragmentation.  What it *might* be saying (but again we can't verify
without an error message) is that your filesystem contains errors that
cannot be fixed in non-interactive mode (i.e. you need to run fsck
manually).

It's hard to tell you what option you need when we are unsure what
problem you are trying to fix.




  reply	other threads:[~2009-10-29 22:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 21:54 [gentoo-user] memory(gray matter) needs jog Maxim Wexler
2009-10-29 22:46 ` Albert Hopkins [this message]
2009-10-30  0:05   ` [gentoo-user] " walt
2009-10-30  0:21     ` Albert Hopkins
2009-10-30  0:26       ` Albert Hopkins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1256856363.135440.6.camel@centar \
    --to=marduk@letterboxes.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox