From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Skylar Burtenshaw <DaninFuchs@gmail.com>
Subject: Re: Can't mount, power failure - recoverable?
Date: Sun, 15 Jul 2012 13:20:14 +0200 [thread overview]
Message-ID: <201207151320.14620.Martin@lichtvoll.de> (raw)
In-Reply-To: <loom.20120714T025232-591@post.gmane.org>
Am Samstag, 14. Juli 2012 schrieb Skylar Burtenshaw:
> Martin Steigerwald <Martin <at> lichtvoll.de> writes:
> > > > Since I didn´t found any explicit mention on it:
> > > > Did you try btrfs-zero-log on the partition prior to mounting it?
>
> I had tried that previously, yes. Approximately the date of my first
> post. Unless something significant has changed in that tool, it seems
> to not be the answer in this case.
>
> > > > All of my BTRFS will not mount after sudden write interruption
> > > > cases have been solved by it. Except one with a BTRFS RAID 0
> > > > with lots of 2 TB drives at a time where I didn´t know about
> > > > btrfs-zero-log. Maybe it would have helped there, too.
>
> Actually, I have about two dozen drives ranging from 250gb to 2tb, but
> I don't think size plays much in this one - I'm obviously just
> guessing here, though.
>
> > Yes.
> >
> > But why would it write some stuff then on mounting?
> >
> > Could it be that it tries to update some of its caches (inode or
> > space)? But then that also does not seem to be in the trace.
>
> I agree with you. I noticed it was trying to write, myself. I have no
> idea what it was doing when the power dropped, I wasn't even present,
> so I can't even say if it was doing some massive database culling or
> just idling.
>
> I noticed there've been some recent (since I last looked at least)
> updates including fsck and such, however I haven't run anything
> git-based since the last time I pulled the btrfs tools, and I had to
> dig for ages to find info on how to get the RECENT stuff from the
> CORRECT source. I can find a dozen Google results that seem relevant,
> but can someone give me a definitive answer on which tree to pull down
> (and how) to test the new tools on my mess?
Hehe, I looked for myself quite some time for it.
Last time I used:
martin@merkaba:~/Linux/Kernel/BTRFS/btrfs-progs> git remote -v
origin git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-
progs.git (fetch)
origin git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-
progs.git (push)
martin@merkaba:~/Linux/Kernel/BTRFS/btrfs-progs> git branch -a
* dangerdonteveruse
master
remotes/origin/HEAD -> origin/master
remotes/origin/dangerdonteveruse
remotes/origin/integration-scrub
remotes/origin/master
remotes/origin/parser
remotes/origin/recovery-beta
But last change in it is:
commit 1957076ab4fefa47b6efed3da541bc974c83eed7
Author: Chris Mason <chris.mason@oracle.com>
Date: Wed Mar 28 12:05:27 2012 -0400
Add incompat flag for big metadata blocks
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Hmmm, master branch seems to be quite current:
commit 8935d8436147f86dfbda3d8b8175a77b654b8abc
Author: David Sterba <dsterba@suse.cz>
Date: Fri Jul 6 10:11:10 2012 -0400
btrfs-progs: mkfs: add option to skip trim
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-07-15 11:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 4:24 Can't mount, power failure - recoverable? Skylar Burtenshaw
2012-03-17 7:51 ` cwillu
2012-03-17 19:06 ` Skylar Burtenshaw
2012-03-18 15:16 ` Chris Mason
2012-03-18 18:49 ` Skylar Burtenshaw
2012-03-19 18:02 ` Chris Mason
2012-03-20 3:06 ` Skylar Burtenshaw
2012-03-26 8:34 ` Skylar Burtenshaw
2012-03-26 8:43 ` Hugo Mills
2012-03-26 8:51 ` Skylar Burtenshaw
2012-03-26 8:44 ` Fajar A. Nugraha
2012-03-26 8:49 ` Skylar Burtenshaw
2012-03-26 8:56 ` Fajar A. Nugraha
2012-07-13 12:23 ` Martin Steigerwald
2012-07-13 12:28 ` Hugo Mills
2012-07-13 14:38 ` Martin Steigerwald
2012-07-14 1:01 ` Skylar Burtenshaw
2012-07-15 11:20 ` Martin Steigerwald [this message]
2012-07-15 11:30 ` Hugo Mills
2012-03-17 10:31 ` Hugo Mills
2012-03-17 19:06 ` Skylar Burtenshaw
2012-03-17 12:18 ` Chris Mason
2012-03-17 19:06 ` Skylar Burtenshaw
2012-07-12 0:47 ` Skylar Burtenshaw
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=201207151320.14620.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=DaninFuchs@gmail.com \
--cc=linux-btrfs@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.