From: Christian Hesse <mail@earthworm.de>
To: Chris mason <chris.mason@oracle.com>
Cc: btrfs-devel@oss.oracle.com, linux-fsdevel@vger.kernel.org
Subject: Re: [Btrfs-devel] [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more)
Date: Mon, 21 Jan 2008 09:57:04 +0100 [thread overview]
Message-ID: <200801210957.06927.mail@earthworm.de> (raw)
In-Reply-To: <200801180848.15634.chris.mason@oracle.com>
On Friday 18 January 2008, Chris mason wrote:
> On Thursday 17 January 2008, Christian Hesse wrote:
> > On Thursday 17 January 2008, Chris mason wrote:
> > > So, I've put v0.11 out there.
> >
> > Ok, back to the suspend problem I mentioned:
>
> [ oopsen ]
>
> > I get this after a suspend/resume cycle with mounted btrfs.
>
> Looks like metadata corruption. How are you suspending?
No, that's not metadata corruption. After reset I can use the image without
problems. After resume the first access to the fs oopses.
I use kernel 2.6.24-rc8 with tuxonice 3.0-rc3 and btrfs 0.11.
Back in early december I reported the problem for btrfs 0.9. Seems like the
lockfs call still is not implemented. Any hints what I need when I try to
code it myself?
--
Regards,
Chris
next prev parent reply other threads:[~2008-01-21 8:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 15:52 [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more) Chris Mason
2008-01-15 16:55 ` Kyle McMartin
2008-01-16 10:02 ` [Btrfs-devel] " Christian Hesse
2008-01-16 17:50 ` Simon Holm Thøgersen
2008-01-16 17:50 ` Simon Holm Thøgersen
2008-01-17 18:25 ` Chris mason
2008-01-17 19:28 ` Daniel Phillips
2008-01-17 20:14 ` Chris mason
2008-01-17 23:17 ` Christian Hesse
2008-01-18 13:48 ` Chris mason
2008-01-21 8:57 ` Christian Hesse [this message]
2008-01-21 9:15 ` Yan Zheng
2008-01-21 10:32 ` Christian Hesse
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=200801210957.06927.mail@earthworm.de \
--to=mail@earthworm.de \
--cc=btrfs-devel@oss.oracle.com \
--cc=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.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 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.