| 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
| ||
|
Message-ID: <20120402223919.GB18000@shiny.nikko.sjc.wayport.net> Date: Mon, 2 Apr 2012 18:39:19 -0400 From: Chris Mason <chris.mason@...cle.com> To: Dave Jones <davej@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org>, linux-btrfs@...r.kernel.org Subject: Re: btrfs io errors on 3.4rc1 On Mon, Apr 02, 2012 at 06:33:50PM -0400, Dave Jones wrote: > On Mon, Apr 02, 2012 at 06:28:02PM -0400, Chris Mason wrote: > > > > x86-64. > > > > > > dmesg below. (ignore the rpc oops, reported elsewhere, it's unrelated) > > > > Well, there really are no btrfs messages in there at all. Do you have > > free space for a clean copy of the btrfs partition? Trying to figure > > out if you have a stale corruption (on two boxes seems really unlikely). > > I definitely can't reproduce it here. > > Don't really have any free space for it (It's the / partition on both) > > Is there a wip btrfs.fsck yet ? One of the machines is just a scratch testbox, > so I'm happy to run it even if it'll potentially make things worse. The current btrfsck repair mode will fix problems in the extent allocation tree, but that probably isn't what you're seeing. I'd just run it read only and see if it finds any problems. (You'll need the FS completely unmounted though). -chris -- 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/
Powered by blists - more mailing lists