linux-um archives
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyich@gmail.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] btrfs failure and BUG_ON behaviour
Date: Sun, 10 Apr 2011 09:56:15 +0300	[thread overview]
Message-ID: <20110410095615.47eedc83@sf> (raw)
In-Reply-To: <BANLkTikjjWR2Ki0aNoTBhecodkGpW2cUzw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1595 bytes --]

On Sat, 9 Apr 2011 23:33:14 +0200
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:

> We have had some problems with the block layer in ~2.6.32 to 2.6.35.
> Commit 4752690 fixed the issues.
> 
> Can you please re-test it with 2.6.38?

Same crash with 2.6.38, so it's either very sneaky btrfs bug or
some discrepancy in ubd.

> Does you script work with other file systems?

Tested on ext4, xfs, jfs and reiserfs3. All survive
the load of creating and deleting 1000 files.

By on-disk load reiserfs3 should be quite similar to btrfs,
so I expected it to show problems, but it didn't.

[n00bish speculation] btrfs also plays games with mm. Maybe
the problem sits somewhere there where block layer/page
cache and on-disk layout gets out-of-sync.

[sf] ~/linux-2.6/fs/btrfs:fgrep -R PageDirty .
./extent_io.c:                          if (!PageDirty(pages[i]) ||
./extent_io.c:          if (!PageDirty(page))
./extent_io.c:          if (!PageDirty(page)) {
./disk-io.c:    if (PageDirty(page))
./disk-io.c:    if (PageWriteback(page) || PageDirty(page))
./disk-io.c:                    if (PageDirty(page)) {
./transaction.c:                                if (PageDirty(page))
./transaction.c:                        if (PageDirty(page)) {
./ioctl.c:              if (PageDirty(page)) {
./inode.c:      if (!page->mapping || !PageDirty(page) || !PageChecked(page)) {
./inode.c:      if (PageWriteback(page) || PageDirty(page))

I'll try to send bug report to linux-btrfs mailing list first
and return if I'll have more details.

-- 

  Sergei

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 250 bytes --]

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev

[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2011-04-10  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09 14:04 [uml-devel] btrfs failure and BUG_ON behaviour Sergei Trofimovich
2011-04-09 21:33 ` richard -rw- weinberger
2011-04-10  6:56   ` Sergei Trofimovich [this message]
2011-04-10 19:58     ` Sergei Trofimovich
2011-04-11 23:13 ` richard -rw- weinberger
2011-04-12 10:13   ` Sergei Trofimovich
2011-04-12 11:22     ` richard -rw- weinberger

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=20110410095615.47eedc83@sf \
    --to=slyich@gmail.com \
    --cc=richard.weinberger@gmail.com \
    --cc=user-mode-linux-devel@lists.sourceforge.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