From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maria =?ISO-8859-1?Q?Wikstr=F6m?= Subject: Re: Kernel BUG at fs/btrfs/inode.c:2281 & 4665 Date: Tue, 12 Apr 2011 22:25:44 +0200 Message-ID: <1302639944.7214.33.camel@localhost> References: <4931fe2bc7e70ddc21f0240f9b65bb29.squirrel@squirrel-webmail.surftown.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: linux-btrfs@vger.kernel.org To: cwillu Return-path: In-Reply-To: List-ID: On tis, 2011-04-12 at 09:29 -0600, cwillu wrote: > On Tue, Apr 12, 2011 at 9:11 AM, wrote: > > > > The computer was idle when the first bug happened and after the reboot > > btrfs can't be mounted. It can't delete orphans and replay the log. > > It would be nice if I can get the data out, there is nothing important > > there but it would be nice. I was actually fixing typos in the backup > > scripts when the bug attacked :) > > There's a "btrfs-zero-log" in the progs-unstable git repository that > will probably get you up and running again. You have to build it > manually via "make btrfs-zero-log". Thanks! It worked, I got the data out :) I found the one who has been crashing the computer every now and then and has probably been corrupting btrfs. scsi_lib.c:1147 So I don't think this is btrfs fault, more likely faulty hardware. > > I have written this by hand so there may be typos. I skipped the parts > > that I don't think is necessary, the rest is on paper if I missed > > something important. > > Digital cameras are wonderful things :p When they have charged batteries ;) // Maria