All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Pazdnikov <pazdnikov@prosoft.ural.ru>
To: <linux-mtd@lists.infradead.org>
Subject: Re: ubifs became broken on contigous power-fails
Date: Wed, 12 May 2010 13:30:07 +0600	[thread overview]
Message-ID: <201005121330.07802.pazdnikov@prosoft.ural.ru> (raw)
In-Reply-To: <E1OBqfw-0002Rs-00.pazdnikov-list-ru@f27.mail.ru>

recovery proccess of ubi2:dbfs prints

ubifs_rcvry_gc_commit: could not find a dirty LEB

but we have plenty of free space

# df
Filesystem                Size      Used Available Use% Mounted on
ubi0:rootfs              13.2M      7.5M      5.7M  57% /
tmpfs                     4.0K         0      4.0K   0% /dev
shm                       1.0M         0      1.0M   0% /dev/shm
tmpfs                     1.0M      8.0K   1016.0K   1% /tmp
tmpfs                     1.0M      4.0K   1020.0K   0% /root
ubi1:logs                11.5M    908.0K     10.0M   8% /var/log
ubi1:tmp                 13.4M     16.0K     12.7M   0% /usr/local/ecom/tmp
ubi0:local                2.1M     64.0K      1.9M   3% /var/local
ubi:config                2.0M     68.0K      1.9M   3% /usr/local/ecom/conf
ubi2:dbfs               169.1M     36.0M    128.4M  22% /usr/local/ecom/db


ubifs/recovery.c: 1044

int ubifs_rcvry_gc_commit(struct ubifs_info *c)
{
	...

	err = ubifs_find_dirty_leb(c, &lp, wbuf->offs, 2);
	if (err) {
		if (err == -ENOSPC)
			dbg_err("could not find a dirty LEB");
		return err;
	}
	ubifs_assert(!(lp.flags & LPROPS_INDEX));
	lnum = lp.lnum;

Why <ubifs_find_dirty_leb> returns -ENOSPC ? we have enough of free space 
according to <df> report

--
Best regards,
Sasha

  reply	other threads:[~2010-05-12  7:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 14:43 ubifs became broken on contigous power-fails Alexander Pazdnikov
2010-05-12  7:30 ` Alexander Pazdnikov [this message]
2010-05-13  8:08   ` Alexander Pazdnikov
2010-05-19 10:36     ` Alexander Pazdnikov
2010-05-20 13:18       ` Alexander Pazdnikov
2010-05-23 11:28 ` Artem Bityutskiy
2010-05-23 12:23   ` Artem Bityutskiy
2010-05-24  6:49     ` Alexander Pazdnikov
2010-05-24  8:18       ` Artem Bityutskiy
2010-05-24  9:50         ` Alexander Pazdnikov
2010-05-24  9:56           ` Artem Bityutskiy
2010-06-12 14:22             ` Artem Bityutskiy
2010-06-15  5:02               ` Alexander Pazdnikov
2010-07-13  3:58                 ` 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=201005121330.07802.pazdnikov@prosoft.ural.ru \
    --to=pazdnikov@prosoft.ural.ru \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pazdnikov@prosoftsystems.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.