linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Hancock <hancockrwd@gmail.com>
To: Felix Miata <mrmazda@earthlink.net>, linux-ide@vger.kernel.org
Subject: Re: HD filesystem integrity issues
Date: Sat, 04 Jan 2014 19:50:29 -0600	[thread overview]
Message-ID: <52C8BA65.3070806@gmail.com> (raw)
In-Reply-To: <52C62FDA.8080904@earthlink.net>

On 01/02/2014 09:34 PM, Felix Miata wrote:
> On 2014-01-02 21:04 (GMT-0600) Robert Hancock composed:
>
>> Felix Miata wrote:
>
>>> http://fm.no-ip.com/Tmp/Linux/dmsgAZBHD201401.txt is dmesg from a STB
>
>> Have you checked the dmesg output? There would likely be some indication
>> of what happened.
>
> Checked for what exactly? That's why I gave it to the list to look at.
> The only thing I recognized as a problem indication was "running e2fsck
> is recommended".

Is that output from after attempting to run e2fsck? It doesn't appear 
that in this output it has even finished recognizing the USB hard drive 
yet. If the OOM killer kicked in, there should be a bunch of output in 
dmesg about it.

>
>> Given that this thing only has 100MB or so of memory,
>> it seems quite likely that the out-of-memory killer kicked in.
>
> As another responder replied within minutes of my post, and you seem to
> have confirmed. It's what I suspected, but I was able to find any way to
> confirm other than to ask somewhere outside the device's so-called
> support forum.
>
>> This isn't really related to linux-ide, the main Linux kernel mailing
>> list would likely be more suitable.
>
> I was thinking a generic filesystem list, but don't know of one about
> ext2/3/4, and thought this better than a high traffic generic list.


      reply	other threads:[~2014-01-05  1:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-01 22:43 HD filesystem integrity issues Felix Miata
2014-01-03  3:04 ` Robert Hancock
2014-01-03  3:34   ` Felix Miata
2014-01-05  1:50     ` Robert Hancock [this message]

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=52C8BA65.3070806@gmail.com \
    --to=hancockrwd@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mrmazda@earthlink.net \
    /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;
as well as URLs for NNTP newsgroup(s).