linux-kernel - Re: [GIT PULL] Btrfs updates for 2.6.35

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201006150717.19886.edt@aei.ca>
Date:	Tue, 15 Jun 2010 07:17:19 -0400
From:	Ed Tomlinson <edt@....ca>
To:	Chris Mason <chris.mason@...cle.com>
Cc:	"linux-kernel" <linux-kernel@...r.kernel.org>,
	linux-btrfs@...r.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 2.6.35

On Monday 14 June 2010 20:47:35 Chris Mason wrote:
> On Mon, Jun 14, 2010 at 03:24:19PM -0400, Ed Tomlinson wrote:
> > On Friday 11 June 2010 15:37:31 Chris Mason wrote:
> > > Hello everyone,
> > > 
> > > The master branch of the btrfs-unstable tree is a collection of fixes
> > > and cleanups, including two btrfs regressions from rc1:
> > > 
> > > git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master
> > > 
> > > One is an freeing blocks on an FS converted from ext34 to btrfs,
> > > and the other is a fallocate fix.
> > > 
> > > The rest are the usual small bug fixes.
> > 
> > Looks like this still misses any fix for the oops I reported May 8th in thread:
> > "[OPPS] btrfs on 33-3 with latest from btrfs-unstable.git master"
> > 
> > Any chance this could be looked into?  I've kept the fs just in case.
> 
> The oops shows a crc failure and then we were not able to read the tree
> block.  Yan Zheng is working on an fsck that can repair things now.
> Until then the best I can do is help copy things off.
> 
> Would you rather save the FS to test fsck?

I can hang on to the FS for a while longer.  One interesting point.  The FS
has both both meta-data and data mirroring enabled.  I gather the oops is
implying that both versions are corrupt.  Btw the fs problem occured after
heavy vm activity caused by running too many kvm(s).

Thanks
Ed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/