public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: David Bergeron <mho.linux-mtd@b2n.ca>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBIFS volume corruption (bad node at LEB 0:0)
Date: Wed, 14 Jan 2009 18:17:34 +0200	[thread overview]
Message-ID: <1231949854.5973.82.camel@localhost.localdomain> (raw)
In-Reply-To: <8EEAB966-52F4-48A3-8FCA-A50BBE8486B7@b2n.ca>

Hi,

I've just upgraded few of my tests to do re-mount testing, and
remounting works fine - I couldn't find any problem.

On Wed, 2009-01-07 at 23:13 -0500, David Bergeron wrote:
> I've cooked up a minimalist test trying to eliminate possible  
> interference.
> The following steps will trigger the corruption almost every time. No  
> errors
> or warnings are produced during this procedure, every step behaves as  
> expected:
> 
> boot kernel ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs ro init=/bin/ 
> bash
> 
> # mount -t proc none /proc
> # ifconfig ...
> # mount -o remount,rw,sync /
> # rsync -aHxvi --delete ... /
> # mount -o remount,ro /
> # reboot -d -f

I wonder what does -d option mean. Could you please try to play with
things like:

1. Try to remove the "sync" parameter of "mount -o remount,rw,sync".
BTW, -o sync makes your rsync work much slower than if you had async
mount and call sync after rsync is done.
2. Try to avoid re-mounting the fs into RO mode, but just call "sync".
3. When you reboot, I guess your boot scripts try to mount the FS in R/O
mode first. Try to tweak them and mount the FS read-write for the first
time.

Please, see what happens, may be this will give us some clue.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  parent reply	other threads:[~2009-01-14 16:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  4:13 UBIFS volume corruption (bad node at LEB 0:0) David Bergeron
2009-01-08  6:46 ` Artem Bityutskiy
2009-01-16 15:34   ` David Bergeron
2009-01-19  8:56     ` Artem Bityutskiy
2009-01-20  3:44       ` David Bergeron
2009-01-20  5:40         ` David Bergeron
2009-01-20  9:01         ` Artem Bityutskiy
2009-01-20 21:47           ` David Bergeron
2009-01-14 16:17 ` Artem Bityutskiy [this message]
2009-01-16 21:23   ` David Bergeron
2009-01-26  9:18 ` Artem Bityutskiy
2009-01-28  2:20   ` Kyungmin Park
2009-01-28  7:51     ` Artem Bityutskiy
2009-01-28  8:24     ` Adrian Hunter
2009-01-29  4:24       ` Kyungmin Park
2009-01-28 16:31   ` David Bergeron

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=1231949854.5973.82.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mho.linux-mtd@b2n.ca \
    /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