public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: "Prins Anton (ST-CO/ENG1.1)" <Anton.Prins@nl.bosch.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: UBIFS failure & stable page writes
Date: Wed, 12 Jun 2013 16:09:41 +0300	[thread overview]
Message-ID: <51B87315.7090808@intel.com> (raw)
In-Reply-To: <85D877DD6EE67B4A9FCA9B9C3A4865670C3F1A3590@SI-MBX14.de.bosch.com>

Can you tar and send fs/ubifs directory?

On 12/06/13 14:57, Prins Anton (ST-CO/ENG1.1) wrote:
> Ok clear!
>
> Regarding mount debug: I suppose I only will see this on the 'first' boot after the problem is in the persistence storage?
> (Up to now I'm not able to signal the point-of-failure... I'm only looking to an (possibly) after recovery situation).
>
> Or makes this sense to do this mount debug on the existing failing device?
>
> FYI: 
> - with 100 devices power cycling every 5 minutes for a weekend we DON'T see a problem.
> - with 100 devices powered on for a weekend and after that give a single power-cycle shows maybe 1 or 2 failing devices (but sometimes '0').
>
> So a main problem in analyzing is the 'moment of failure' and 'reproduction (rate)'.
>
> Met vriendelijke groeten | Best Regards, 
> Anton Prins
>
> Met vriendelijke groeten | Best Regards, 
> Anton Prins
>
>
> -----Original Message-----
> From: Adrian Hunter [mailto:adrian.hunter@intel.com] 
> Sent: woensdag 12 juni 2013 14:00
> To: Prins Anton (ST-CO/ENG1.1)
> Cc: dedekind1@gmail.com; linux-mtd@lists.infradead.org
> Subject: Re: UBIFS failure & stable page writes
>
> On 12/06/13 14:13, Prins Anton (ST-CO/ENG1.1) wrote:
>> Does it make sense to use chk_orphans?
> That checks for missing orphans but the problem is the opposite: the
> presence of orphans that should not be there.
>
>> I suppose I have to do: $ echo "1" > chk_orphans
>>
>> Or am I wrong?
>>
>> Met vriendelijke groeten | Best Regards, 
>> Anton Prins
>>

  reply	other threads:[~2013-06-12 13:04 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <85D877DD6EE67B4A9FCA9B9C3A4865670C3E8CB9B7@SI-MBX14.de.bosch.com>
     [not found] ` <4BE1E71893EF1E4F9E9DD99FB4EBF0032C02EA2D44@SI-MBX02.de.bosch.com>
     [not found]   ` <85D877DD6EE67B4A9FCA9B9C3A4865670C3E8CBA85@SI-MBX14.de.bosch.com>
2013-05-27 12:18     ` UBIFS failure & stable page writes Jan Kara
2013-05-27 13:13       ` Prins Anton (ST-CO/ENG1.1)
2013-05-28  2:57         ` Artem Bityutskiy
2013-05-28  7:07           ` Prins Anton (ST-CO/ENG1.1)
2013-05-28  7:44             ` Artem Bityutskiy
2013-05-28  8:18               ` Prins Anton (ST-CO/ENG1.1)
2013-05-28  9:11                 ` Artem Bityutskiy
2013-05-28 11:13                   ` Prins Anton (ST-CO/ENG1.1)
2013-05-29  6:49                     ` Artem Bityutskiy
2013-05-29 11:06                       ` Prins Anton (ST-CO/ENG1.1)
2013-05-31  9:51                       ` Prins Anton (ST-CO/ENG1.1)
2013-06-03  6:01                         ` Artem Bityutskiy
2013-06-11 12:16                           ` Prins Anton (ST-CO/ENG1.1)
2013-06-12  7:58                             ` Adrian Hunter
2013-06-12  8:28                               ` Prins Anton (ST-CO/ENG1.1)
2013-06-12 11:40                                 ` Adrian Hunter
2013-06-12 11:13                               ` Prins Anton (ST-CO/ENG1.1)
2013-06-12 12:00                                 ` Adrian Hunter
2013-06-12 11:57                                   ` Prins Anton (ST-CO/ENG1.1)
2013-06-12 13:09                                     ` Adrian Hunter [this message]
2013-06-12 13:57                                       ` Prins Anton (ST-CO/ENG1.1)
2013-06-13 10:54                                         ` Mats Kärrman
2013-06-13 13:31                                           ` Prins Anton (ST-CO/ENG1.1)
2013-06-13 13:41                                             ` Adrian Hunter
2013-06-13 14:02                                               ` Prins Anton (ST-CO/ENG1.1)
2013-06-15 22:25                                             ` Mats Kärrman
2013-06-13 19:24                                           ` Prins Anton (ST-CO/ENG1.1)
2013-06-15 22:45                                             ` Mats Kärrman
2013-06-17 11:20                                               ` Prins Anton (ST-CO/ENG1.1)
2013-06-18  6:31                                               ` Prins Anton (ST-CO/ENG1.1)
2013-06-18  7:01                                                 ` Adrian Hunter
2013-06-18  7:17                                                   ` Prins Anton (ST-CO/ENG1.1)
2013-06-25  8:21                                                   ` Prins Anton (ST-CO/ENG1.1)
2013-06-28  9:05                                                     ` Mats Kärrman
2013-06-28  9:27                                                       ` Prins Anton (ST-CO/ENG1.1)
2013-07-25 13:18                                                       ` Prins Anton (ST-CO/ENG1.1)
2013-06-12  7:12                           ` Prins Anton (ST-CO/ENG1.1)
2013-05-28 13:00                   ` Prins Anton (ST-CO/ENG1.1)
2013-06-13  7:41                     ` Adrian Hunter
2013-05-28  8:15           ` Prins Anton (ST-CO/ENG1.1)
2013-05-28  9:09             ` Artem Bityutskiy

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=51B87315.7090808@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=Anton.Prins@nl.bosch.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.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