linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jon Ringle <jon@ringle.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: detecting that ubifs switched to ro after problem
Date: Sun, 13 Jun 2010 13:07:03 +0300	[thread overview]
Message-ID: <1276423623.19028.213.camel@localhost> (raw)
In-Reply-To: <1276422454.19028.209.camel@localhost>

On Sun, 2010-06-13 at 12:47 +0300, Artem Bityutskiy wrote:
> On Fri, 2010-06-11 at 22:46 -0400, Jon Ringle wrote:
> > Hi,
> > 
> > I'd like to be able to somehow detect that ubifs has taken the action
> > of switching from rw to ro due to some error detected in the ubifs
> > filesystem. If I can detect this then maybe I can do something about
> > it, such as copying the ubifs contents to a .tar.bz2 in /tmp,
> > mkfs.ubifs, and restore .tar.bz2 back again.
> > 
> > Is there a way I can do this?
> 
> I think with 2fde99cb55fb9d9b88180512a5e8a5d939d27fec you can check for
> R/O state from /proc/mounts. Also, you can use something like inotify to
> watch /proc/mounts changes and react if UBIFS became r/o.

Just added:

http://www.linux-mtd.infradead.org/faq/ubifs.html#L_detect_ro

for your convenience.

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

  reply	other threads:[~2010-06-13 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-12  2:46 detecting that ubifs switched to ro after problem Jon Ringle
2010-06-13  9:47 ` Artem Bityutskiy
2010-06-13 10:07   ` Artem Bityutskiy [this message]
2010-06-14 15:15   ` Jon Ringle
2010-06-16  6:44     ` 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=1276423623.19028.213.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=jon@ringle.org \
    --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;
as well as URLs for NNTP newsgroup(s).