But what are you doing to the filesystem when it crashes? How did you
mount it?
Lee
On Wed, Feb 25, 2009 at 08:03:01AM -0600, Mitch Harder (aka DontPanic) wrote:
I've been creating a local git repository of full btrfs-unstable sources.
I'll create a new branch off the master branch, and
On Wed, Feb 25, 2009 at 11:05:58AM -0500, Lee Trager wrote:
But what are you doing to the filesystem when it crashes? How did you
mount it?
In my case, it's mounted with this fstab entry:
/dev/media/scratch /media/vlad/video/video btrfs noatime,nosuid,nodev
0 0
and I can
The messages attached are only WARNING messages.
I have not been encountering a crash, nor does the data seem to get
corrupted in my case (as far as I can tell).
Btrfs seems to actually work fine, except for the large amount of log messages.
On Wed, Feb 25, 2009 at 10:13 AM, Hugo Mills
On Tue, 2009-02-24 at 23:02 +, Hugo Mills wrote:
This is essentially a repost of a mail I made last week, to which I
didn't get a reply.
Sorry I missed replying to this one last week, thanks for resending.
I'm getting huge numbers of kernel warnings whilst using
btrfs. They're all
[ resend with the list cc'd ]
On Wed, 2009-02-25 at 12:50 -0600, Mitch Harder (aka DontPanic) wrote:
I'll try to test that out.
I had just noticed that some of my kernel configuration settings (not
sure which ones) seem to affect the clean_tree_block warnings I've
been getting, and one of
This is essentially a repost of a mail I made last week, to which I
didn't get a reply.
I'm getting huge numbers of kernel warnings whilst using
btrfs. They're all warn_slowpath, and all seem to be in
fs/btrfs/disk-io.c. I've included one typical example at the end of
this mail.
Kernel
I have also been getting similar warnings filling up my logs.
However, in my case, I have been experimenting with back-porting btrfs
to a 2.6.28 kernel. So I've been waiting for the back-porting efforts
to get a little further along.
But I thought I'd respond in case this information helps.
Mitch, I haven't seen any problems using BTRFS and my patch on 2.6.28 or
2.6.27, what are you doing to cause this error? Are you using the latest
sources from btrfs-unstable?
Lee
Mitch Harder (aka DontPanic) wrote:
I have also been getting similar warnings filling up my logs.
However, in my
